Confirmed breach. Intrusion Aug 10, 2024–Aug 12, 2024, discovered Aug 12, 2024 — the first regulatory filing landed 280 days later (flagged late). 12,204 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)
12,204
Data types
—
Jurisdictions
2
MT NH
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Aug 10, 2024 → Aug 12, 2024
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Aug 12, 2024
Reported by NEW HAMPSHIRE AG filing
280 days
⛰️New Hampshire State AGFirst filinglinked via multistate filing link · 100%
Community Hospital of Anaconda notified the NH Attorney General of a data security incident discovered on August 12, 2024. Unauthorized access occurred between August 10-12, 2024. One NH resident was affected. CHA engaged cybersecurity experts, notified the FBI, and offered credit monitoring services.
Community Hospital of Anaconda reported a data breach to the Montana Attorney General. The breach was reported on 2025-05-19. The breach occurred from 08/10/2024 to 08/12/2024. 12,203 Montana residents were affected.
Affected (this filing): 12,203
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.