Community Hospital of Anaconda
bd_9ec20b09bece6ce7 · schema v1 · pii pii-v1
Full breach record for Community Hospital of Anaconda →2 incidents on fileThreat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Meow on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
The Community Hospital of Anaconda, located in Anaconda, Montana, is a healthcare facility dedicated to providing comprehensive medical services to the local community. It offers a range of services including emergency care, inpatient and outpatient treatments, surgical procedures, and specialized care. The hospital is committed to delivering high-quality, patient-centered care in a compassionate and supportive environment.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Sep 30, 2024
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (4) · sorted by filing gap
- New Hampshire State AGbd_73babd6817fd19492025-05-19 · +230dVerified
- HHS OCRbd_7b0652d2e93faddc2025-05-19 · +230dVerified
- Nebraska State AGbd_8c32d664856dbe6c2025-05-19 · +230dCandidate
- Montana State AGbd_b21460dfd81a982c2025-05-19 · +230dVerified
Filing propagation · 5 filings · 3 states
View merged incident ↗Pattern: first filing Sep 30, last May 19 (MT) — a 230-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
meow
According to ransomware.live, Meow emerged in 2022 (resurfacing aggressively in 2024), initially operating as a RaaS using the Conti v2 codebase before transitioning to a data-extortion-only model — selling stolen data rather than encrypting files — with a heavy focus on US healthcare and medical research organizations.