DisclosureLens
MONTANAHackingHealthcareHealthcareCustomer Data InvolvedPHIHealth (basic)Identity (basic)Medium

Community Hospital of Anaconda

bd_7b0652d2e93faddc · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

May 19, 2025

To disclose

—

Affected

21,243

Linked

5 filings

Confidence

69%
Full breach record for Community Hospital of Anaconda →2 incidents on file

Community Hospital of Anaconda reported to HHS on 2025-05-19 a Hacking/IT Incident affecting 21243 individuals. Breached information located on Network Server.

Leak gap clock✗ Leak >180d
⚠ no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.
⚠ No discovery dateThe OCR public portal omits the discovery date, so the 60-day notification clock cannot be evaluated from this source — only that the filing was submitted.

Incident timeline — partial

? — ?

Breach window unknown

May 19, 2025

Filed

—

Corroborated · see linked filings

Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.

This filing is one of 5 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?

Ransomware claims (1)

Regulatory filings (3) · sorted by filing gap

Filing propagation · 4 filings · 3 states

View merged incident ↗
New Hampshire State AGMay 19 · first
Nebraska State AGMay 19 · first
Montana State AGMay 19 · first
HHS OCRMay 19 · first · this page

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.