DataBreaches.Net

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

KS: Labette Health discloses October, 2021 data security incident

Posted on March 12, 2022 by Dissent

Labette Health in Kansas has started notifying employees and patients of a data security incident.

According to a statement on their website, an investigation determined that unauthorized individual(s) potentially accessed and acquired information from portions of their network between October 15, 2021 and October 24, 2021.

It appears that it took them four months from the time of the attack until they determined what was accessed and whose files were accessed or acquired:

On February 11, 2022, following an extensive review and analysis of the data at issue, Labette Health determined that certain files and folders that may have been accessed or acquired contained identifiable personal and/or protected health information of employees and certain patients who received services from Labette Health, including the individuals’ full name and one or more of the following (to the extent it resided on Labette Health’s system): Social Security number, medical treatment and diagnosis information, treatment costs, dates of service, prescription information, Medicare or Medicaid number, and/or health insurance information. This incident does not affect all patients of Labette Health and Labette Health does not necessarily maintain all of the information listed above for all patients.

Labette Health’s statement indicates that it has no evidence to suggest that any information has been misused, and as of the time of this publication, DataBreaches.net has not seen any indication that data from this incident have been dumped on any leak site (but of course, some threat actors do not dump data until many months later, so vigilance is required). Disturbingly, once again, we see language that suggests notification is voluntary when it appears to be actually required:

However, out of an abundance of caution, on March 11, 2022, Labette Health sent written notification to anyone whose information may have been contained in the impacted files and folders and for whom it had enough information to determine a physical address.

“…out of an abundance of caution”? Entities are required to notify patients under these circumstances. In this blogger’s opinion, entities should not be suggesting that they are going above and beyond their obligations when they are actually just complying with what HIPAA and HITECH require of entities when they cannot provide compelling evidence that would make notification optional or unnecessary.

You can read their full website notice here.

This incident has not yet appeared on HHS’s public breach tool, so we do not yet have any number affected by this incident.

Category: Breach IncidentsHackHealth Data

Post navigation

← Ubisoft says it experienced a ‘cyber security incident’, LAPSUS$ group claims credit for attack
Another Technology Management Resources client reports a data breach →

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

  • Data breach of patient info ends in firing of Miami hospital employee
  • Texas DOT investigates breach of crash report records, sends notification letters
  • PowerSchool hacker pleads guilty, released on personal recognizance bond
  • Rewards for Justice offers $10M reward for info on RedLine developer or RedLine’s use by foreign governments
  • New evidence links long-running hacking group to Indian government
  • Zaporizhzhia Cyber ​​Police Exposes Hacker Who Caused Millions in Losses to Victims by Mining Cryptocurrency
  • Germany fines Vodafone $51 million for privacy, security breaches
  • Google: Hackers target Salesforce accounts in data extortion attacks
  • The US Grid Attack Looming on the Horizon
  • US govt login portal could be one cyberattack away from collapse, say auditors

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

  • California county accused of using drones to spy on residents
  • How the FBI Sought a Warrant to Search Instagram of Columbia Student Protesters
  • Germany fines Vodafone $51 million for privacy, security breaches
  • Malaysia enacts data sharing rules for public sector
  • U.S. Enacts Take It Down Act
  • 23andMe Bankruptcy Judge Ponders Trump Bill’s Injunction Impact
  • Hell No: The ODNI Wants to Make it Easier for the Government to Buy Your Data Without Warrant

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.