Deaconess Health System — December 2025 breach
Clustered 5 records across 3 jurisdictions: 4 filings and 1 leak-site claim · filing window Mar 20, 2026 → Aug 7, 2026 (dated filings only). View entity profile → Other incidents for this victim →
incident inc_6455cd18f5bf455a · merged by human · confidence 100%
Litigation Timing
SupplementalRange of discovered_at dates across filings
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.
Sensitive data
identity_governmentIncident timeline
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
- JAN 7Leak siteworldleaks postfirst record · attacker claim · unverifiedoperator-confirmedday 0
- MAR 1IL AGIL AG noticefiling day not on record · no count statedoperator-confirmed—
- MAR 20HHS OCRHHS OCR noticestates nationwide total 8,941operator-confirmed+72d
- AUG 1IL AGIL AG noticefiling day not on record · no count statedauto-linked—
- AUG 7TX AGTX AG noticemost recent · states nationwide total 203,874operator-confirmed+212d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Dec 2, 2025 – Dec 18, 2025 TX AG
- Discovered
- Feb 2, 2026IL AGJun 26, 2026IL AG + TX AGfilings disagree on discovery
- Data types
- Financial account · Health (basic) · Identity (basic) · Government ID · PHI IL AG + HHS OCR + TX AG
- 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)
203,874
Sum of filed state slices
374· 0.2% of stated
100% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.
Evidence ladder — rungs this incident occupies
Attacker assertion only. Establishes: claim date, group, alleged victim.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
Merge provenance
- Method
- human
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- Reviewed
- operator-reviewed Aug 25, 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
140 days
vs. multi-state median
23.3× 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.