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

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.