Discord Inc.
bd_7f5fe7fdfa6c96b9 · schema v1 · pii pii-v1
Full breach record for Discord Inc. →2 incidents on fileDiscord Inc. disclosed that a third party obtained unauthorized access to its customer service platform via a compromised vendor device between September 20-22, 2025. The incident was discovered on September 25, 2025. Affected data includes names, contact info, dates of birth, government IDs, limited payment info, IP addresses, and support messages. Discord revoked vendor access, engaged forensics, notified law enforcement, and offered 12 months of credit monitoring.
J jump to incidentP pin to compareR raw source
Incident timeline
Sep 20, 2025
Begins
Sep 25, 2025
Discovered
Feb 6, 2026
Filed
vs. sector median
on median
Linked disclosures
Why this link?Regulatory filings (7) · sorted by filing gap
- Vermont State AGbd_83d20831ef0a9cc92025-12-29 · +39dVerified
- Texas State AGbd_a591e2f5f8077ec02025-12-05 · +63dVerified
- New Hampshire State AGbd_9f1c7efe99906a6a2025-12-01 · +67dVerified
- California State AGbd_c70a5de9bd46eff82025-11-26 · +72dCandidate
Show 3 more filings ↓Show fewer ↑up to 97d gap
- Montana State AGbd_ded551c03660a6312025-11-26 · +72dVerified
- Indiana State AGbd_78e85d3aaf14ec302025-11-24 · +74dVerified
- Illinois State AGbd_44d3ff8b5d6f1e9e2025-11-01 · +97dVerified
Filing propagation · 8 filings · 8 states
View merged incident ↗Pattern: first filing Nov 1 (IL), last Feb 6 (MA) — a 97-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.