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

AT&T INC. — June 2019 breach

Clustered 13 filings across 13 jurisdictions · filing window Mar 30, 2024 → Jul 12, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

13 filings

States

13

Affected · reported

51,226,382

First → last filing

Mar 30, 2024 → Jul 12, 2024

Merge confidence

100%

incident inc_90620f5d30194d40 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 13 regulatory filings. The filings describe a third-party compromise. Intrusion Jun 1, 2019–Apr 25, 2024, discovered Mar 17, 2024 — the first regulatory filing landed 13 days later (flagged late). 51,226,382 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Credentials, and 6 more. Notifications rolled out on a 104-day schedule across 13 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
33days

Range of discovered_at dates across filings

Materiality delta
84days

Discovery to SEC materiality determination

SEC filing delay
0days

Materiality determination to SEC 8-K filing

Filing span
104days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence — no leak-site claim in this cluster.

Regulatory clocksLeak gap✗ Leak >180dFull 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 filing
Jul 12, 2024most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. MAR 30WI AGWI AG noticefirst filing · 7,600,000 affectedday 0
  2. APR 1IL AGIL AG noticeno count stated+2d
  3. APR 9VT AGVT AG noticeno count stated+10d
  4. APR 9CA AGCA AG noticeno count stated+10d
  5. APR 9SC AGSC AG notice1,060,051 SC residents+10d
  6. APR 9IN AGIN AG noticestates nationwide total 51,226,382+10d
  7. APR 9MT AGMT AG notice70,747 MT residents+10d
  8. APR 10WA AGWA AG notice378,471 WA residents+11d
  9. APR 10MA AGMA AG notice161,272 MA residents+11d
  10. APR 10OR AGOR AG noticestates nationwide total 51,226,382+11d
  11. APR 15NH AGNH AG notice61,130 NH residents+16d
  12. APR 25DE AGDE AG noticeno count stated+26d
  13. JUL 12SEC 8-KSEC 8-K noticemost recent · no count stated+104d
  14. 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
VT AG
Discovered
Mar 17, 2024IL AGMar 26, 2024VT AG + CA AG + SC AG +4Apr 19, 2024SEC 8-Kfilings disagree on discovery
Data types
Authentication · Credentials · Financial account · Financial credentials · Identity (basic) · Government ID · Location · Metadata · PII
WI AG + VT AG + CA AG +7
Attack vector
Third-Party / Supply Chain
VT 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)

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 statement1 member

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

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

104 days

Cadence

~1 / 8.7d

vs. multi-state median

13.0× 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.