Discord Data Breach – What You Need to Know. Featured
Attackers accessed a third-party support system; Discord says ~70,000 ID photos were exposed while hackers claim far broader impact.
What Happened?
On September 20, 2025, attackers gained unauthorized access to a third-party customer support system used by Discord. Discord says this was not a breach of Discord’s core platform, but of a vendor used for customer service. The company revoked the vendor’s access, launched an internal investigation, engaged a leading forensics firm, and notified law enforcement.
Meanwhile, the threat actors claim they accessed Discord’s Zendesk environment for 58 hours using credentials tied to a support agent at an outsourced provider. They allege they stole ~1.6 TB of data, including ticket attachments and transcripts. They demanded a ransom (reportedly reduced from $5M to $3.5M) and threatened to leak data.
What Information Was Exposed?
Discord states the incident impacted “a limited number of users” who interacted with Customer Support or Trust & Safety. Confirmed potentially exposed data includes:
- Personally identifying information (PII) you provided to support (name, username, email, phone).
- Messages/attachments sent to support (including screenshots or documents).
- Photos of government IDs (driver’s license or passport) for about 70,000 users who submitted age-verification appeals.
- Partial billing information for some users (payment type, last four digits, and purchase history linked to the account).
- IP addresses associated with support interactions.
The attackers claim the scope is much larger—millions of tickets and users—and that internal integrations made some payment-related details retrievable. These broader claims have not been independently verified.
Who is Affected?
You may be affected if you:
- Opened or replied to a Discord support ticket, including Trust & Safety, around or before September 20, 2025; or
- Submitted age-verification documents (government ID photo).
Discord estimates ~70,000 users’ ID photos were exposed; the attackers allege more. A named vendor, 5CA, says its systems were not breached and that the incident occurred outside its environment. Zendesk says the issue did not stem from a Zendesk platform vulnerability.
What You Can Do Now
- Watch for notice from Discord and follow its instructions.
- Monitor financial accounts and consider a fraud alert or credit freeze with major bureaus if your ID may be involved.
- Replace your government ID if advised or if you suspect misuse.
- Enable/refresh multi-factor authentication on Discord and email; be alert to phishing that references your past support tickets.
- Review purchase history and dispute unfamiliar charges.
- Document everything (emails, dates, screenshots)—this can help your legal options.
Free Case Review (No Obligation)
If you interacted with Discord’s support or submitted an ID and are concerned your information was exposed, you may have legal rights. Complete the short form on this page, and a data breach lawyer will contact you to discuss your situation, eligibility, and next steps. There is no cost to find out where you stand.