DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed8 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 8 filings

Discord Inc. — September 2025 breach

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

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

74,729

First → last dated filing

Nov 24, 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. 74,729 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 74-day schedule across 7 dated filings beginning Nov 24, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
3days

Range of discovered_at dates across filings

Filing span
74days

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

Sensitive data

identity_government

Incident timeline

Sep 20, 2025breach begins
Sep 22, 2025discovered · members disagree
Nov 24, 2025first dated filing
Feb 6, 2026most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. NOV 1IL AGIL AG noticefiling day not on record · no count stated—
  2. NOV 24IN AGIN AG noticefirst filing · states nationwide total 74,729day 0
  3. NOV 26MT AGMT AG notice13 MT residents+2d
  4. NOV 26CA AGCA AG noticeno count stated+2d
  5. DEC 1NH AGNH AG notice39 NH residents+7d
  6. DEC 5TX AGTX AG noticestates nationwide total 74,729+11d
  7. DEC 29VT AGVT AG noticeno count stated+35d
  8. FEB 6MA AGMA AG noticemost recent · 283 MA residents+74d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 20, 2025
IN AG
Discovered
Sep 22, 2025NH AGSep 25, 2025IL AG + MT AG + CA AG +3filings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · Location · PII
IL AG + MT AG + CA AG +4
Attack vector
Third-Party / Supply Chain
MT AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

74,729

Sum of filed state slices

2,025· 2.7% of stated

97% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US74,729
TX1,465
MA283
IN225
NH39
MT13

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing8 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

74 days

Cadence

~1 / 12.3d

vs. multi-state median

12.3× slower

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

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.