DataBreaches.Net

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

LivaNova to notify U.S. patients of October 2023 ransomware incident (1)

Posted on April 26, 2024 by Dissent

A press release from medical technology firm LivaNova PLC  indicates that patients of LivaNova U.S. are being notified of a breach first disclosed in November of 2023.  An investigation at the time indicated that their systems were first accessed without authorization on or around October 26, 2023, but it was not until April 10, 2024 that they learned that personal information of U.S. patients was also involved.

The information varied by individual but may have included name, contact information (e.g., phone number, email and postal addresses), Social Security number, date of birth, medical information (e.g., treatment, condition, diagnosis, prescription, physician, medical record number and device serial number), and health insurance information.

They do not disclose how many U.S. patients have been affected or why it took more than four months to discover patients were affected. The incident has not yet appeared on HHS’s public breach tool.

Ransomware Attacks

Although they did not call it a ransomware attack in their press release, the LivaNova incident was claimed by LockBit on their leak site in December 2023. At the time, LockBit claimed to have acquired 2.2 TB of data from the firm and threatened to release it publicly if LivaNova did not pay. LivaNova’s press release makes no mention of any ransom or extortion demand or their response to any demand. DataBreaches has yet to determine whether LockBit ever released the LivaNova data or not, but LivaNova’s statement does not indicate whether they have scoured or continue to scour the dark web to see if any data has shown up.

The LockBit incident was not the first ransomware attack report involving LivaNova. In March 2021, Conti claimed to have successfully attacked them. At the time, Health IT Security reported that Conti leaked data, but from the reporting, it’s not clear whether U.S. patient data was included in that leak.

Update: LivaNova reported this to HHS on April 26 as impacting 180,000 patients.


Related:

  • Attorney General James Announces Settlement with Wojeski & Company Accounting Firm
  • JFL Lost Up to $800,000 Weekly After Cyberattack, CEO Says No Patient or Staff Data Was Compromised
  • A business's cyber insurance policy included ransom coverage, but when they needed it, the insurer refused to pay. Why?
  • Massachusetts hospitals Heywood, Athol say outage was a cybersecurity incident
  • The Alliance That Wasn’t: A Critical Analysis of ReliaQuest’s Q3 2025 Ransomware Report
  • Heritage Provider Network $49.99M Class Action Settlement
Category: BlogHealth DataMalware

Post navigation

← Wealthy Taxpayers Alerted to Leaked Data Years After IRS Breach
Unsecured Health Genie bucket exposed almost 450,000 files with patient data — Cybernews →

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

  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs
  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says

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

  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[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.