Discord Inc. — September 2025 breach

Clustered 8 filings across 8 jurisdictions · filing window Nov 1, 2025 → Feb 6, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

Affected · reported

74,729

First → last filing

Nov 1, 2025 → Feb 6, 2026

Merge confidence

100%

incident inc_321298994a914512 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe a third-party compromise. Intrusion Sep 20, 2025–Sep 22, 2025, discovered Sep 22, 2025 — the first regulatory filing landed 40 days later (flagged late). 74,729 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 97-day schedule across 8 filings beginning Nov 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

40days

Discovered → first regulatory filing

Discovery variance

3days

Range of discovered_at dates across filings

Filing span

97days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksTexas✗ TX AG >30dVermont✗ VT AG >45 bdayMassachusetts✗ MA AG >90dCalifornia✓ CA 60-day OK · 8dFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.