HackingCustomer Data InvolvedPIIIDENTITY_BASICLowContained
Community Hospital of Anaconda
bd_73babd6817fd1949 · schema v1 · pii pii-v1
Full breach record for Community Hospital of Anaconda →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.
Leak gap clock✗ Leak >180d40 weeks discovery → filing
⚠ unattributedNo provenance was recorded for this discovery date and it matches no other date on the record. It may be correct, but it is not independently grounded.
This filing is one of 2 about the same incident.View merged incident
A leak claim by meow about this victim predates this filing by 230 days.View originating leak claim
Linked disclosures
Why this link?Regulatory filings (1) · sorted by filing gap
- bd_b21460dfd81a982cMontana State AGfiled 2025-05-19Candidate
Source provenance
- Source URL
- https://mm.nh.gov/files/uploads/doj/remote-docs/community-hospital-anaconda-20250519.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
- Filed at
- May 19, 2025
- Raw hash
- 0b44fbec01865ec095ab7ac4f18b40e9d02d929aad9ce2f05a1ceff724d33b5c
Reporting entity
- Name
- Community Hospital of Anacondanorm: community hospital of anaconda
- Domain
- communityhospitalofanaconda.org
Victim entity
- Name
- Community Hospital of Anacondanorm: community hospital of anaconda
- Domain
- communityhospitalofanaconda.org
Incident
- Discovered
- Aug 12, 2024
- Materiality determined
- —
- Notification sent
- May 19, 2025
- Affected individuals
- 1
- Data types
- PIIIDENTITY_BASIC
- Attack vector
- Unauthorized Access
- MITRE ATT&CK
- T1078 Valid Accounts
- Threat actor
- External
- Regulator citations
- Notified the Federal Bureau of Investigation
Compliance
- Time to disclose
- 40 weeks(280 days from discovery to filing)
- Compliance flags
- Leak >180d
- Discovery-date grounding
- unattributedNo provenance was recorded for this discovery date and it matches no other date on the record. It may be correct, but it is not independently grounded.
Extraction provenance
- Status
- No extraction artifact recorded for this disclosure.