Clustered 3 filings across 3 jurisdictions · filing window Nov 17, 2023 → Jun 6, 2024. View entity profile → Other incidents for this victim →
incident inc_6e4b1f727a834dcc · merge_method llm · 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.
PHI · Identity (basic) · Government ID
NH VT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 1, 2023 → Nov 30, 2023
When the intrusion reportedly occurred, per the linked filings
Nov 1, 2023
Reported by VERMONT AG filing
A family-owned organization for more than 50 years, PruittHealth provides a seamless network of post-acute care services and resources, offering skilled nursing care, home ...
PruittHealth notified consumers of a November 2023 cyber incident where illegal foreign actors attacked its network, potentially exfiltrating PHI, SSNs, and financial data. Hackers demanded ransom and threatened to publish data on the dark web. Forensic investigators were engaged. Exposure is unconfirmed but possible.
PruittHealth, Inc. reported a cybersecurity incident involving unauthorized access to its network. The breach affected approximately 10,000 individuals in New Hampshire, exposing personal and health information. The company engaged forensic investigators and offered credit monitoring to affected individuals.
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): 10,000