DataBreaches.Net

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

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:

  • Two more entities have folded after ransomware attacks
  • British institutions to be banned from paying ransoms to Russian hackers
  • Data breach feared after cyberattack on AMEOS hospitals in Germany
  • Microsoft Releases Urgent Patch for SharePoint RCE Flaw Exploited in Ongoing Cyber Attacks
  • Global hack on Microsoft product hits U.S., state agencies, researchers say
  • Premier Health Partners issues a press release about a breach two years ago. Why was this needed now?
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

  • Scattered Spider Hijacks VMware ESXi to Deploy Ransomware on Critical U.S. Infrastructure
  • Hacker group “Silent Crow” claims responsibility for cyberattack on Russia’s Aeroflot
  • AIIMS ORBO Portal Vulnerability Exposing Sensitive Organ Donor Data Discovered by Researcher
  • Two Data Breaches in Three Years: McKenzie Health
  • Scattered Spider is running a VMware ESXi hacking spree
  • BreachForums — the one that went offline in April — reappears with a new founder/owner
  • Fans React After NASCAR Confirms Ransomware Breach
  • Allianz Life says ‘majority’ of customers’ personal data stolen in cyberattack (1)
  • Infinite Services notifying employees and patients of limited ransomware attack
  • The safe place for women to talk wasn’t so safe: hackers leak 13,000 user photos and IDs from the Tea app

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

  • Congress tries to outlaw AI that jacks up prices based on what it knows about you
  • Microsoft’s controversial Recall feature is now blocked by Brave and AdGuard
  • Trump Administration Issues AI Action Plan and Series of AI Executive Orders
  • Indonesia asked to reassess data privacy terms in new U.S. trade deal
  • Meta Denies Tracking Menstrual Data in Flo Health Privacy Trial
  • Wikipedia seeks to shield contributors from UK law targeting online anonymity
  • British government reportedlu set to back down on secret iCloud backdoor after US pressure

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.