Singing River Health System Singing River Health System is both a mission-driven provider of health services and one of the largest employers on the Mississippi Gulf Coast.
Clustered 3 filings across 3 jurisdictions · filing window Sep 10, 2023 → Jan 12, 2024. View entity profile → Other incidents for this victim →
incident inc_56c261561f2342e2 · merge_method human · confidence 100%
Discovered → first regulatory filing
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.
MT VT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 16, 2023 → Aug 18, 2023
When the intrusion reportedly occurred, per the linked filings
Aug 19, 2023
Reported by VERMONT AG filing
Singing River Health System Singing River Health System is both a mission-driven provider of health services and one of the largest employers on the Mississippi Gulf Coast.
Singing River Health System notified consumers of a ransomware attack discovered on August 19, 2023, with unauthorized access occurring between August 16-18, 2023. Impacted data included names, DOBs, addresses, SSNs, and medical/health information. The organization engaged forensic specialists and offered credit monitoring services. No evidence of misuse was found.
Singing River Health System - Singing River Gulfport reported a data breach to the Montana Attorney General. The breach was reported on 2024-01-12. The breach occurred from 8/16/2023 to 8/18/2023. 35 Montana residents were affected.
Affected (this filing): 35
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.