DataBreaches.Net

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

Memorial Hospital and Manor notifies 120,085 people of November ransomware attack

Posted on February 15, 2025February 16, 2025 by Dissent

On November 3, 2024, WALB in Georgia reported that Memorial Hospital and Manor had been the victim of a ransomware attack on November 1 that they discovered on November 2. The hospital announced the incident on its Facebook page in a post that is no longer available.

But Memorial Hospital and Manor did not appear to have notified HHS of the breach at all — not even with a placeholder to indicate an unknown number of patients affected.

On February 8, the hospital notified the Maine Attorney General’s Office of the incident, reporting that a total of 120,085 people were affected. And yet no notice has appeared on HHS’s public breach tool even now.

Memorial Hospital & Manor (“MH-M”) subsequently posted a substitute notice on its website dated February 10. In their notice, they refer to a data security incident but never use the word “ransomware” or indicate the individual or group that attacked them.  The notice does state, however, that an unauthorized individual accessed and acquired information that may have included patient name, Social Security number, date of birth, health insurance information, and medical treatment and/or history information.

MH-M states that they promptly notified the FBI of the incident. They make no mention of notifying HHS, and as of publication, there is still no incident reported on HHS’s public breach tool.

But of greater concern is MH-M’s total silence about the fact that this was a ransomware attack and the attackers have dumped the data they acquired.

Embargo Leaks the Data

Although MH-M does not seem to have informed patients that their protected health information has been leaked on the dark web, it has been leaked. The Embargo ransomware group had claimed to have acquired 1.15 TB of files, which they dumped when MH-M did not meet their demands for payments.

DataBreaches examined parts of the data tranche and also reached out to Embargo to ask whether the hospital had ever responded to them at all or attempted to negotiate with them.

A spokesperson for Embargo informed DataBreaches that yes, MH-M had attempted to negotiate:

“they offer 500k, we declined”

DataBreaches is not implying any criticism of MH-M for not paying ransom. What this site is questioning is why HHS was not notified and why it hasn’t informed to warn patients that their data has been leaked.

DataBreaches sent an inquiry to MH-M on February 14 asking both questions. There has been no reply as of publication.


Related:

  • KT Chief to Resign After Cybersecurity Breach Resolution
  • Cyber-Attack On Bectu’s Parent Union Sparks UK National Security Concerns
  • 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
  • John Bolton Indictment Provides Interesting Details About Hack of His AOL Account and Extortion Attempt
  • UK: 'Catastrophic' attack as Russians hack files on EIGHT MoD bases and post them on the dark web
Category: Breach IncidentsCommentaries and AnalysesHealth DataHIPAAMalwareOf Note

Post navigation

← Virginia AG’s office says it was struck by ‘sophisticated cyberattack’
Bill raising the bar for class-action suits in data breach incidents advances →

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

  • Lawmakers Warn Governors About Sharing Drivers’ Data with Federal Government
  • 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

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.