IMA — December 2025 breach

Clustered 9 filings across 9 jurisdictions · filing window May 29, 2026 → Jun 1, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

Affected · reported

525,306

First → last filing

May 29, 2026 → Jun 1, 2026

Merge confidence

100%

incident inc_2e4baa417d484cd8 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. Intrusion Dec 8, 2025–Dec 16, 2025, discovered Dec 16, 2025 — the first regulatory filing landed 164 days later (flagged late). 525,306 individuals reported across the linked filings. Data reported: Government ID, Financial account, Identity (basic), and 4 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

164days

Discovered → first regulatory filing

Discovery variance

139days

Range of discovered_at dates across filings

Filing span

3days

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 clocksCalifornia✗ CA 60-day late · 164dWashington✗ WA AG >90dMaine✓ ME AG ≤30d · 25dSouth Carolina✓ SC CRA notice 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.