Kootenai Health
bd_9bec957b67b78ee0 · schema v1 · pii pii-v1
Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Threeam 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
Founded in 1966, Kootenai Health is a hospital that provides patient care services for people in Idaho, Montana, and Eastern Washington. They are based in Coeur d'Alene, Idaho. ...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Mar 25, 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 (10) · sorted by filing gap
- HHS OCRbd_12ca7637998f0d3a2024-04-24 · +30dVerified
- Illinois State AGbd_d60e84d88ca3d0932024-08-01 · +129dVerified by operator
- New Hampshire State AGbd_196109db99161bff2024-08-12 · +140dVerified by operator
- California State AGbd_7207145d3a1eee732024-08-12 · +140dVerified by operator
Show 6 more filings ↓Show fewer ↑up to 142d gap
- Maine State AGbd_bbd64450e7d998702024-08-12 · +140dVerified by operator
- Indiana State AGbd_c536f51a1acc533b2024-08-12 · +140dVerified by operator
- Montana State AGbd_c76c2ab47183bfe82024-08-12 · +140dVerified by operator
- Washington State AGbd_9a0d2aaa103665ed2024-08-13 · +141dVerified by operator
- Oregon State AGbd_e32a5cabcecf51a32024-08-13 · +141dVerified by operator
- Massachusetts State AGbd_26ce553c58cb69262024-08-14 · +142dVerified by operator
Filing propagation · 11 filings · 10 states
View merged incident ↗Pattern: first filing Mar 25, last Aug 14 (MA) — a 142-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.
threeam
According to ransomware.live, A new Ransomware family identified by the name '3AM' or 'ThreeAM' in September 2023. The ransomware operation was observed by the Symantec team, in which a ransomware affiliate attempted to deploy another ransomware, LockBit, on the target network and then switched to 3AM when LockBit was reportedly blocked. > > The ransomware operation, according to the publication on its Tor-based website, has been operating since mid-August 2023, according to the publication from its first victim. Source: https://github.com/crocodyli/ThreatActors-TTPs