DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed8 records · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedpearhigh sensitivity
Merged incident · 8 records

Iroquois Memorial Hospital — October 2025 breach

Clustered 8 records across 5 jurisdictions: 7 filings and 1 leak-site claim · filing window Jan 9, 2026 → Oct 16, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 records

States

5

Affected · reported

219,437

First → last dated filing

Jan 9, 2026 → Oct 16, 2026

Merge confidence

100%

incident inc_fb4adf72ac214ec8 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Oct 8, 2025–Nov 15, 2025, discovered Nov 10, 2025. 219,437 individuals reported across the linked filings. Data reported: Government ID, Health (basic), PHI, and 2 more. Notifications rolled out on a 280-day schedule across 5 dated filings beginning Jan 9, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
291days

Range of discovered_at dates across filings

Filing span
280days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap✗ Leak >180dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 8, 2025breach begins
Nov 10, 2025discovered · members disagree
Jan 9, 2026first dated filing
Oct 16, 2026most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. NOV 25Leak sitepear postfirst record · attacker claim · unverifiedday 0
  2. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  3. JAN 9HHS OCRHHS OCR noticestates nationwide total 621+45d
  4. SEP 29TX AGTX AG noticestates nationwide total 219,437+308d
  5. OCT 1MA AGMA AG noticefiling day not on record · 281 MA residents—
  6. OCT 14NH AGNH AG notice11 NH residents+323d
  7. OCT 14VT AGVT AG notice5 VT residents+323d
  8. OCT 16TX AGTX AG noticemost recent · states nationwide total 217,703+325d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 8, 2025 – Nov 15, 2025
MA AG
Discovered
Nov 10, 2025MA AG + NH AGDec 31, 2025IL AGAug 28, 2026TX AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
IL AG + HHS OCR + TX AG +3
Attack vector
Unauthorized Access
HHS OCR

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)

219,437

Sum of filed state slices

1,576· 0.7% of stated

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

US219,437
TX1,279
MA281
NH11
VT5

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing7 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
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 21, 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

280 days

Cadence

~1 / 70d

vs. multi-state median

46.7× slower

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.