DataBreaches.Net

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

Highlands Oncology Group notifies 113,575 people after ransomware attack by Medusa

Posted on August 2, 2025 by Dissent

On August 1, Highlands Oncology Group in Arkansas notified the Maine Attorney General’s Office of a ransomware attack it discovered on June 2, when certain files and systems were inaccessible. Investigation into the incident revealed that there had been unauthorized access at times between January 21, 2025, and June 2, 2025.

On June 19, the Medusa gang had added Highlands to its leak site with a price tag of $700,000.00 to delete the data or download it. A countdown clock indicated a deadline of July 21.

Highlands’ report to Maine indicated that a total of 113,575 people were affected by this attack. A check of Medusa’s leak site today does not find Highlands listed or leaked. DataBreaches has sent an inquiry to Medusa asking them to confirm whether the listing was removed or not. If it was removed, it could mean that Highlands paid an extortion demand to have Medusa delete the data, but there could be other explanations. DataBreaches will update this post if Medusa replies.

The incident has not yet shown up on HHS’s public breach tool, but Highlands has posted a substitute notice on its website, linked from the home page. The notice discloses that it was a ransomware attack, but makes no mention of any extortion demand and whether any data showed up on the internet.

A Previous Ransomware Attack

The Medusa ransomware incident is not Highlands’ first ransomware incident. On December 22, 2023, Highlands notified HHS of an incident affecting 55,297 patients. HHS investigated and their closing statement reads:

The covered entity (CE), Highlands Oncology Group, reported that it experienced a ransomware incident that affected the protected health information (PHI) of 55,297 individuals. The PHI involved included names, addresses, dates of birth, Social Security numbers, claims information, diagnoses, conditions, lab results, medications, and other treatment information. The CE notified HHS, the affected individuals, and the media. In response to the breach, the CE implemented additional system monitoring safeguards, revised policies regarding remote access, and implemented additional technical safeguards.

In response to the recent breach, Highlands’ substitute notice states:

Highlands Oncology is committed to maintaining the privacy and security of the information entrusted to it. Highlands has taken, and is taking, additional steps to help reduce the likelihood of a similar event from happening in the future, including enhancing its technical security measures.

Given that there was unauthorized access beginning in January, and the incident involved exfiltration of files and then encryption, what will HHS find and do when they investigate this incident?

Category: Breach IncidentsHealth DataHIPAAMalwareU.S.

Post navigation

← Oklahoma Substantially Amends Its Data Breach Notification Statute
HCA Healthcare settled two lawsuits this week; one was over its 2023 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

  • 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
  • The Case for Making EdTech Companies Liable Under FERPA
  • NHS providers reviewing stolen Synnovis data published by cyber criminals

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

  • 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
  • Who’s watching the watchers? This Mozilla fellow, and her Surveillance Watch map

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.