State AGConfirmed10 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 10 filings
SafetyFirst — January 2026 breach
Clustered 10 filings across 10 jurisdictions · filed Jul 23, 2026 (dated filings only). View entity profile → Other incidents for this victim →
⚠ 2 cross-filing discrepancies →Merge100%
incident inc_4c9414671aa34560 · merged by deterministic · confidence 100%
Confirmed breach. Merged as one breach: 10 regulatory filings. Intrusion Jan 16, 2026–Jan 19, 2026, discovered Jan 19, 2026. 141,230 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Each member filing remains the legal record for its jurisdiction.
Litigation Timing
SupplementalDiscovery variance
65days
Range of discovered_at dates across filings
Filing span
0days
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 clocksOregon✗ OR AG >45dWashington✗ WA AG >90dCalifornia✗ CA 30-day late · 185dTexas✗ TX AG >30dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline
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.