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.
Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
21,226
Data types
3
PII · Identity (basic) · Government ID
Jurisdictions
2
MT SC
Linked filings
3
HHS OCR · State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jan 19, 2022
When the intrusion reportedly occurred, per the linked filings
Genesis Health Care, Inc. reported a phishing incident in South Carolina on September 2, 2022, affecting 3,862 individuals. The breach involved the compromise of personal information, including names and government identifiers, via a phishing attack. The company notified affected individuals and completed impact assessments.
Affected (this filing): 3,862
🌴SOUTH CAROLINAHHS OCRlinked via same-victim cross-source · 100%
Genesis Health Care, Inc. reported to HHS on 2022-09-02 a ransomware attack affecting 21,226 individuals. Breached information located on Network Server. The incident involved PHI including names, addresses, DOB, SSNs, and financial/claims data. The entity implemented safeguards and provided credit monitoring.
Affected (this filing): 21,226
HHS notified
🦬Montana State AGMost recentlinked via multistate filing link · 100%
Genesis Health Care, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2022-09-02. The breach occurred from 1/19/2022 to 4/11/2022. 1 Montana residents were affected.
Affected (this filing): 1
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.