HopeHealth — March 2025 breach
Clustered 2 filings across 1 jurisdiction · filing window May 15, 2025 → Jul 11, 2025. View entity profile → Other incidents for this victim →
incident inc_dc1104a4558d4248 · merged by llm · confidence 50%
Litigation Timing
SupplementalDiscovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Incident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- MAY 15HHS OCRHHS OCR noticefirst filing · states nationwide total 5,823day 0
- JUL 11SC AGSC AG noticemost recent · 5,716 SC residents+57d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Mar 19, 2025 – Mar 20, 2025 SC AG
- Discovered
- Mar 20, 2025· 1d undetected SC AG
- Data types
- Health (basic) · Identity (basic) · PHI · PII HHS OCR + SC 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)
5,823
Sum of filed state slices
5,716· 98.2% of stated
2% 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
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
Merge provenance
- Method
- llm
- Confidence
- 0.50 · below the 0.85 auto-merge floor
- Audit
- Every link edge records its method, confidence and model + prompt versions (50% is the strongest edge).
Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.
Filing velocity
Spread
57 days
vs. multi-state median
7.1× 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.