Currency:USD $
Notifications
WowCarry BlogBlogGuides & news
Gaming News guide

Discord 2025 Support Incident: Data Exposure and User Notices

Read Discord's October 2025 incident details: possible ID-photo and limited billing exposure, excluded data, official user notices and 5CA's account.

Discord 2025 Support Incident: Data Exposure and User Notices4 minutes
On this pageWhat Discord Reported in October 20251 / 5

What Discord Reported in October 2025

Discord said approximately 70,000 users might have had government-ID photos exposed in an incident involving customer-support data. That estimate concerned possible exposure of ID photos used for age-related appeals. It was not a total for every potentially affected data category or a count of individual image files.

This report covers the October 2025 public statements. Discord published its incident notice on October 3 and updated it on October 9, 2025. It described unauthorized access connected with a third-party customer-service provider and users who had contacted Customer Support or Trust & Safety.

Which Data Was Potentially Involved?

The distinctions below follow Discord's account of the incident. Information in a support ticket is a different category from ordinary server conversations or private messages outside support.

Data categoryWhat Discord reported
Contact informationNames, Discord usernames, email addresses and other contact details supplied to support could be involved.
Billing informationPotential exposure included payment type, a card's last four digits and purchase history. Discord excluded full card numbers and card security codes.
Support conversationsMessages exchanged with customer-service agents could be involved. Discord excluded messages and activity beyond what users discussed with support.
IP addressesListed among the potentially involved information.
Government-ID imagesAbout 70,000 users might have had photos exposed. Discord said the individual notification would specify whether ID exposure applied.
Passwords and authentication dataListed as excluded from this incident.
Corporate informationLimited records such as training materials and internal presentations were listed as potentially involved.

Limited billing exposure still matters. Saying full card numbers were excluded does not mean no payment-related information could be involved. Equally, the support-message category does not establish access to a user's general Discord message history.

Check the Individual Notice and Use Official Support

For this incident, Discord's stated notification method was email from [email protected]. At the time of its announcement, it said it was contacting impacted users. The notice also said Discord would not call users about this incident.

  1. Read the account-specific notification. Check what it says about the information connected with your support contact, rather than treating every category in the general announcement as confirmed for your account.
  2. Look for the ID-photo statement. Discord said possible ID exposure would be specified in the email. The public 70,000 estimate alone does not identify an individual account.
  3. Use the official Discord Help Center for questions. The notification sender is not presented here as an address to which you should send documents or a reply.
  4. Stay alert to suspicious follow-up contact. That was Discord's recommendation to affected users. Refer back to its published notice if an unexpected caller claims to be handling this incident.

The October 2025 announcement described its notification process at that time. It does not establish a new notification campaign in 2026.

Discord's Account and 5CA's Statement

The public record contains statements from two parties. Keep their descriptions attributed when considering how access occurred:

October 3, 2025: Discord's initial notice

Discord disclosed unauthorized access involving its third-party customer-support services. It said the attacker sought data to extort a ransom.

October 9, 2025: Discord's updated notice

The updated account named 5CA and identified the approximately 70,000 users with possible ID-photo exposure. Discord said its own platform was not breached.

October 14, 2025: 5CA's statement, marked updated October 27

In its holding statement and FAQ, 5CA denied a breach of its own systems. It described preliminary findings involving one employee and access to the client's third-party support ticketing system. It also said it did not handle government-issued IDs.

5CA said the client would have to confirm the extent of data taken because the activity occurred outside 5CA's systems. Its account distinguished its own platforms from the client's ticketing environment; the statement described an ongoing investigation rather than a final independent finding.

What Response Steps Were Reported?

Discord said it revoked the provider's ticketing access, engaged a computer-forensics firm and law enforcement, notified relevant data-protection authorities, and reviewed detection and third-party security controls.

5CA said it revoked the employee's access, suspended the employee while investigating, increased monitoring and added blocking measures. Those were the company's reported actions, not independently tested assurances about every system or user.

The useful boundaries are the affected support-data categories, the individual notice and the attributed investigation statements. The reviewed sources do not settle a final forensic cause or establish that every person who previously contacted support had ID documents exposed.

Cover image: Discord's official incident notice.

Play more. Grind less.

Explore help for the game you are playing.

Browse game services