DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed9 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 9 filings

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

9

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

Sensitive data

identity_government

Incident timeline

Dec 8, 2025breach begins
Dec 16, 2025discovered · members disagree
notification delay · 164 days
May 29, 2026first filing
Jun 1, 2026most 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. MAY 29MA AGMA AG noticefirst filing · 934 MA residentsday 0
  2. MAY 29OR AGOR AG noticestates nationwide total 525,306day 0
  3. MAY 29NH AGNH AG notice200 NH residentsday 0
  4. MAY 29VT AGVT AG notice40 VT residentsday 0
  5. MAY 29IN AGIN AG noticestates nationwide total 525,306day 0
  6. MAY 29ME AGME AG noticeno count statedday 0
  7. MAY 29CA AGCA AG noticeno count statedday 0
  8. MAY 29WA AGWA AG notice1,977 WA residentsday 0
  9. JUN 1SC AGSC AG noticemost recent · 70,266 SC residents+3d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 8, 2025 – Dec 16, 2025
OR AG
Discovered
Dec 16, 2025NH AG + CA AG + WA AG +1May 4, 2026ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
MA AG + NH AG + VT AG +4
Attack vector
Unauthorized Access
MA 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)

525,306

Sum of filed state slices

76,809· 14.6% of stated

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

US525,306
SC70,266
IN3,392
WA1,977
MA934
NH200
VT40

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 filing9 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 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

3 days

Cadence

~1 / 0.4d

vs. multi-state median

2.7× faster

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.