DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Kootenai Health sends notifications for 464,088 people after February attack

Posted on August 13, 2024 by Dissent

More than five months after discovering an attack that disrupted access to some of its IT systems, Kootenai Health is sending notification letters to 464,088 patients, employees, and employees’ dependents.

Kootenai Health describes itself as providing a comprehensive range of medical services to patients in north Idaho, eastern Washington, Montana and the Inland Northwest at several facility locations. In a sample notification letter submitted to the Maine Attorney General on behalf of Kootenai Health and its subsidiaries Kootenai Clinic, Kootenai Outpatient Surgery and Kootenai Outpatient Imaging (collectively “Kootenai Health”), they write:

On March 2, 2024, Kootenai Health became aware of unusual activity that disrupted access to certain IT systems. Upon discovering this activity, we took steps to secure our digital environment. We also engaged leading cybersecurity experts to assist with an investigation and to determine whether personal information may have been accessed or acquired without authorization. The investigation revealed that an unknown actor may have gained unauthorized access to certain data from the Kootenai Health network on or about February 22, 2024.

The types of information may include names, dates of birth, Social Security numbers, driver’s license or government-issued identification numbers, medical record numbers, medical treatment and condition details, medical diagnoses, medication information and health insurance information.

Kootenai’s website version of the notice has two sentences of note that the template sent to Maine omits:

To date, Kootenai Health is not aware of any attempt to misuse any of the information potentially involved in this incident.

and

While we are not aware of the misuse of any affected individual’s information, we are providing the following information to help those who want to know more about steps they can take to protect themselves and their personal information:

What We Still Don’t Know

DataBreaches initially contacted Kootenai Health on March 25 after threat actors known as ThreeAM (3am) listed them on their dark web leak site on March 24 but without any proof that they had acquired data from Kootenai. No reply from Kootenai was received, but on April 3, Kootenai Health issued a press release.

DataBreaches called Kootenai Health twice earlier today to ask some questions, but they did not return the calls by publication. Here are the questions we had for them:

1. Kootenai’s notice mentioned disrupted access. Were any patient files or employee files encrypted?
2. Did Kootenai negotiate with the 3am attackers at all?
3. Kootenai’s notification does not mention that 3am dumped 9.5 gb of files. What is in those files?
4. Do they believe patients and employees should be told if 3am dumped their personal data on the internet?
5. Has HHS been notified of this breach? No notice has appeared on HHS as of publication.
6. How many of the 464,088 people affected were patients, including employees or their dependents who may have received medical services from the system or health insurance?

Category: Breach IncidentsHealth DataMalwareU.S.

Post navigation

← Leader of International Malvertising and Ransomware Schemes Extradited from Poland to Face Cybercrime Charges
Update: Gramercy Surgery Center attackers leaked patient data going back 20 years (1) →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • CoinMarketCap Hacked, Scrambles to Remove Malicious Wallet Verification Popup
  • Montana Attorney General launches investigation into Lee Enterprises data breach
  • AT&T gets preliminary approval for $177 million data breach settlement
  • Aflac notifies SEC of breach suspected to be work of Scattered Spider
  • Former JBLM soldier pleads guilty to attempting to share military secrets with China
  • No, the 16 billion credentials leak is not a new data breach — a wake-up call about fake news (Updated)
  • Tonga’s health system hit by cyberattack (1)
  • Russia Expert Falls Prey to Elite Hackers Disguised as US Officials
  • Proposed class action settlement in In re Netgain Technology litigation
  • Qilin Offers “Call a lawyer” Button For Affiliates Attempting To Extort Ransoms From Victims Who Won’t Pay

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • The Markup caught 4 more states sharing personal health data with Big Tech
  • Privacy in the Big Sky State: Montana’s Consumer Privacy Law Gets Amended
  • UK Passes Data Use and Access Regulation Bill
  • Officials defend Liberal bill that would force hospitals, banks, hotels to hand over data
  • US Judge Invalidates Biden Rule Protecting Privacy for Abortions
  • DOJ’s Data Security Program: Key Compliance Considerations for Impacted Entities
  • 23andMe fined £2.31 million for failing to protect UK users’ genetic data

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net

Mastodon: Infosec.Exchange/@PogoWasRight

Signal: +1 516-776-7756

DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.