DataBreaches.Net

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

Esse Health provides update about April cyberattack and notifies 263,601 people (1)

Posted on July 1, 2025July 2, 2025 by Dissent

Update: Esse Health notified Maine that a total of 263,601 people were affected, but they notified HHS that 23,671 patients were affected.  

Esse Health has notified the Maine Attorney General’s Office that 263,601 people were affected by an incident they first disclosed in early May.

Esse has 45 locations in and around the St. Louis metropolitan area. According to their notices and update of June 20, 2025, Esse first became aware of unusual activity on its system on April 21, 2025. It subsequently confirmed that an unauthorized individual accessed and exfiltrated data.

Media coverage in May indicated that this was a ransomware attack, but Esse’s website update of June 20 made no mention of whether there was any encryption of their files. They may have been unable to access their patient records because they took their system offline while they were securing it and investigating the attack.

According to their notice, the data involved varied by individual but may have included information such as name, address, date of birth, health insurance information, medical record number, patient account number, and certain health information.

There was no indication that social security numbers were involved. Nor was there any indication as of their last update that any of the involved information had been misused.

No threat actor group appears to have ever claimed responsibility for the attack, which raises questions as to whether there ever was a demand, and if so, was it paid. DataBreaches emailed Esse Health to ask whether there had been any encryption, whether there had been any ransom demand, and if so, who signed the demand. DataBreaches also asked why the PHI of more than 263,000 patients hadn’t been encrypted if it was connected to the internet, and whether it was old data or current data, or both.  No reply was available by publication, but this post will be updated if a reply is received.

 


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
  • A business's cyber insurance policy included ransom coverage, but when they needed it, the insurer refused to pay. Why?
  • Before Their Telegram Channel Was Banned Again, ScatteredLAPSUS$Hunters Dropped Files Doxing Government Employees (2)
Category: Breach IncidentsHealth DataU.S.

Post navigation

← Terrible tales of opsec oversights: How cybercrooks get themselves caught
CMS Sending Letters to 103,000 Medicare beneficiaries whose info was involved in a Medicare.gov 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.