Confirmed breach. Intrusion Nov 2, 2024, discovered Nov 4, 2024 — the first regulatory filing landed 269 days later (flagged late). 11,912 individuals reported across the linked filings.
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 clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
11,912
Data types
—
Jurisdictions
2
IN NH
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Nov 4, 2024
When the intrusion reportedly occurred, per the linked filings
Breach discoveredletter-grounded
Nov 4, 2024
Reported by NEW HAMPSHIRE AG filing
269 days
⛰️New Hampshire State AGFirst filinglinked via multistate filing link · 100%
Good Samaritan Health Center of Cobb notified the NH AG of a cybersecurity incident discovered on Nov 4, 2024. Unauthorized access potentially exposed patient PII, SSNs, financial info, and PHI. One NH resident affected. Response included forensic investigation, system security enhancements, and 12 months of credit monitoring.
Good Samaritan Health Center of Cobb reported a data breach to the Indiana Attorney General. The breach occurred on 2024-11-02 and was reported on 2025-08-04. 2 Indiana residents were affected. 11,912 individuals affected in total.
Affected (this filing): 11,912
Leak >180d
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.