All incidents View linkage analytics →Get the evidence package — $7.99 what’s inside →

Confirmed11 records · 10 statesUnverified claimConfirmedEnforcedmedusacritical sensitivity

Merged incident · 11 records

SimonMed Imaging — January 2025 breach

Clustered 11 records across 10 jurisdictions: 10 filings and 1 leak-site claim · filing window Mar 27, 2025 → Oct 14, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 records

States

Affected · reported

1,275,669

First → last dated filing

Mar 27, 2025 → Oct 14, 2025

Merge confidence

100%

incident inc_9297a6f9f74649a5 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 1 unverified claim. The filings describe hacking. Intrusion Jan 21, 2025–Feb 5, 2025, discovered Jan 27, 2025 — the first regulatory filing landed 59 days later; 2 later filings were flagged late. 1,275,669 individuals reported across the linked filings. Data reported: Government ID, Biometric, Health (basic), and 6 more. Notifications rolled out on a 201-day schedule across 8 dated filings beginning Mar 27, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

59days

Discovered → first regulatory filing

Discovery variance

1days

Range of discovered_at dates across filings

Leak precedence

45days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span

201days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dVermont✗ VT AG >45 bdayTexas✗ TX AG >30dFull 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.