GLOBALClaimed by Hunters InternationalFirst sightinglinked via shared-victim match · 100%
Posted to leak site Oct 28, 2023bd_4756da0f31313954
Country : United States of America - Exfiltraded data : yes - Encrypted data : no
Clustered 4 filings across 3 jurisdictions · filing window Oct 28, 2023 → Aug 15, 2024. View entity profile → Other incidents for this victim →
incident inc_db476a31c55e4f32 · merge_method deterministic · confidence 100%
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
IN OH
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 12, 2023
When the intrusion reportedly occurred, per the linked filings
Country : United States of America - Exfiltraded data : yes - Encrypted data : no
At Carespring, we are committed to providing top-quality health care management services to our patients. Whether you need skilled nursing, independent living, assisted living, memory care facilities, or rehabilitative services, we have the expertise...
Carespring Health Care Management LLC reported to HHS on 2024-08-15 a Hacking/IT Incident affecting 64,609 individuals. Breached information located on Network Server. The breach exposed PHI including names, addresses, DOB, SSN, driver's license, financial info, diagnoses, lab results, and medications. The entity implemented security safeguards and retrained staff.
Carespring Health Care Management LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2023-10-12 and was reported on 2024-08-15. 653 Indiana residents were affected. 76,719 individuals affected in total.
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.
Affected (this filing): 64,609
Affected (this filing): 76,719