All incidents View linkage analytics →Get the evidence package — $7.99 what’s inside →

Confirmed12 filings · 12 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 12 filings

AT&T INC. — June 2019 breach

Clustered 12 filings across 12 jurisdictions · filing window Mar 30, 2024 → Apr 25, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

Affected · reported

51,226,382

First → last dated filing

Mar 30, 2024 → Apr 25, 2024

Merge confidence

100%

incident inc_90620f5d30194d40 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. The filings describe a third-party compromise. Intrusion Jun 1, 2019–Mar 26, 2024, discovered Mar 17, 2024 — the first regulatory filing landed 13 days later. 51,226,382 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Credentials, and 4 more. Notifications rolled out on a 26-day schedule across 11 dated filings beginning Mar 30, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

13days

Discovered → first regulatory filing

Discovery variance

9days

Range of discovered_at dates across filings

Filing span

26days

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 clocksVermont✓ VT AG ≤14 bdayCalifornia✓ CA 60-day OK · 6dSouth Carolina✓ SC CRA notice dueWashington✓ WA AG ≤30dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

authenticationfinancial_credentialsidentity_government

Incident timeline

Jun 1, 2019breach begins

Mar 17, 2024discovered · members disagree

notification delay · 13 days

Mar 30, 2024first dated filing

Apr 25, 2024most 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

MAR 30WI AGWI AG noticefirst filing · 7,600,000 affectedoperator-confirmedday 0
APR 1IL AGIL AG noticefiling day not on record · no count statedauto-linked—
APR 9VT AGVT AG noticeno count statedauto-linked+10d
APR 9CA AGCA AG noticeno count statedauto-linked+10d
APR 9SC AGSC AG notice1,060,051 SC residents+10d
APR 9IN AGIN AG noticestates nationwide total 51,226,382auto-linked+10d
APR 9MT AGMT AG notice70,747 MT residentsauto-linked+10d
APR 10WA AGWA AG notice378,471 WA residentsauto-linked+11d
APR 10MA AGMA AG notice161,272 MA residentsauto-linked+11d
APR 10OR AGOR AG noticestates nationwide total 51,226,382auto-linked+11d
APR 15NH AGNH AG notice61,130 NH residentsauto-linked+16d
APR 25DE AGDE AG noticemost recent · no count statedauto-linked+26d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Jun 1, 2019 – Jun 30, 2019
Discovered: Mar 17, 2024IL AGMar 26, 2024VT AG + CA AG + SC AG +4filings disagree on discovery
Data types: Authentication · Credentials · Financial account · Financial credentials · Identity (basic) · Government ID · PII
Attack vector: Third-Party / Supply Chain

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)

51,226,382

Sum of filed state slices

10,768,749· 21.0% of stated

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

US51,226,382

WI7,600,000

IN1,437,078

SC1,060,051

WA378,471

MA161,272

MT70,747

NH61,130

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 filing12 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 Aug 17, 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

26 days

Cadence

~1 / 2.6d

vs. multi-state median

4.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.