People search Discord data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 5 Discord-linked incidents, with headline counts up to 70K+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why Discord breach history matters
Discord operates in Software (United States). Across indexed rows, recurring themes include cloud and database misconfiguration, third-party and supply-chain exposure. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2026 — Persona age verification frontend exposure
Cataloged incident. Security researchers discovered frontend components from identity vendor Persona exposed on the open web, linked to Discord's age verification system. The exposed material did not grant direct access to user data but revealed structural details about how the verification flow operates. Discovery surfaced on X and spread across cybersecurity circles, adding pressure to Discord's 2026 compliance plans. Exposed categories include Structural/architectural details of age verification flow; no direct user data. No attested victim count is published for this row yet. See the discord2026-persona and canonical BreachHistory entry.
2025 — 70k IDs
Cataloged incident. Hackers compromised a third-party vendor responsible for age verification, exposing government ID photos of approximately 70,000 Discord users. Affected users primarily from UK and Australia. Exposed data included government ID photos, names, email addresses, contact details, IP addresses, and messages with customer service. No full credit card numbers or passwords were accessed. Exposed categories include Government ID photos, names, email addresses, contact details, IP addresses, customer service messages. BreachHistory cites approximately 70K+ affected records in this row. See the discord2025 and canonical BreachHistory entry.
2025 — third-party support breach
Cataloged incident. Discord experienced a security incident in 2025 when third-party customer support services were hacked. Limited numbers of names, usernames, emails, IP addresses, and billing information were exposed. Exposed categories include Names, usernames, emails, IP addresses, limited billing information. No attested victim count is published for this row yet. See the discord2025a and canonical BreachHistory entry.
2023 — Third-party customer service agent account compromised
Cataloged incident. A third-party customer service agent's account was compromised, exposing support tickets, email addresses, and message contents for a subset of users. Exposed categories include Support tickets; email addresses; message contents. No attested victim count is published for this row yet. See the discord2023 and canonical BreachHistory entry.
2021 — — User data
Cataloged incident. Third-party. User data. Exposed categories include Names, emails, addresses, and other PII. No attested victim count is published for this row yet. See the discord2021 and canonical BreachHistory entry.
Patterns and analysis
- Cloud and database misconfiguration — appears across multiple Discord catalog entries; prioritize controls that address this class of failure.
- Third-party and supply-chain exposure — appears across multiple Discord catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Bookmark the Discord company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/discord · Latest: discord2026-persona.
Sources: BreachHistory catalog (5 rows for Discord), company and regulator disclosures cited in individual breach records.