Esse Health System

An April 21, 2025, intrusion at Esse Health disrupted patient communications, records access and some appointments while offices remained open. The provider confirmed file copying and reported phones and primary patient-facing systems restored by June 2; ransomware and attribution remain unresolved.
Unauthorized access to systems, accounts, networks, or data.
An unauthorized party accessed or viewed data without evidence that the data was copied, removed, altered, or publicly disclosed.
Data was copied, transferred, downloaded, or otherwise removed from the affected environment by an unauthorized party.
Authorized users could not access required data because of the incident, even when the data was not encrypted, deleted, or destroyed.
A service, system, platform, or operational capability remained available only in part or with significant limitations.
Telephone, voice-over-IP, call-center, or related voice communication services were unavailable or materially impaired.
Internal business, administrative, operational, or staff-facing systems were unavailable.
Staff, customers, patients, students, residents, or other users could not access records or case information normally.
Appointment, booking, reservation, dispatch, staffing, or other scheduling functions were unavailable or impaired.
Clinical, diagnostic, pharmacy, patient-care, medical-record, or other healthcare operations were materially affected.
Services continued but with longer processing, response, delivery, or completion times.
Staff or users had to rely on paper, telephone, in-person, offline, or other manual processes.
The organization redirected users to a different website, office, telephone number, email address, provider, or service channel.
Employees or contractors were unable to perform normal duties because systems, data, facilities, or communications were unavailable.
Customers, residents, patients, students, vendors, or members of the public faced access restrictions or could not use services normally.
The incident may involve extortion, but available evidence does not establish which extortion indicators were present.
Esse Health’s April 2025 cyber incident interrupted outpatient care and access to network-dependent information in the St. Louis area. The provider’s own notice dates suspicious activity and unauthorized network access to April 21. It says an intruder viewed and copied files. These findings establish a confirmed cyber incident and data theft with high confidence; they do not establish the initial access technique or a ransomware family.
Our May 7 report described continued disruption. In First Alert 4’s May 6 reporting, named patients described difficulty transferring records and an April 30 appointment canceled because the office could not access records. The provider confirmed that it was investigating unusual network activity with outside specialists. These are concrete consequences for patient services, beyond a privacy incident alone.
Esse Health said its offices remained open and continued serving patients while some network systems were offline. It used backup processes and directed patients to text their doctor’s office or use the patient portal because telephone capabilities were limited. Continued office operations therefore coexisted with delayed or canceled care and impaired communication.
A May 13 update reported restored information-sharing functions and improved ability to schedule appointments, while warning that phone limitations continued. By its June 2 update, the provider said phones and other primary patient-facing network systems had been restored and regular contact channels were available again. The operational incident is resolved on that evidence. The reviewed updates establish restoration by June 2, without identifying the exact final restoration day; the prior draft’s May 26 end date is unsupported.
The provider’s current notice identifies potentially involved contact details, birth dates, insurance information, patient and medical record identifiers, and certain health information, varying by person. It also includes Social Security numbers for a limited subset. That qualified primary finding takes precedence over July 1 reporting that said no Social Security numbers were stolen. The same report put initial notifications at 263,601 individuals; that is an attributed historical notification count.
Esse Health said its electronic medical record system was not accessed or copied. This does not contradict patients’ inability to obtain records during the outage: availability to patients and staff is a different question from intruder access to that system. The evidence does not establish that every office or patient experienced the same disruption.
The July report suggested ransomware as a possibility based on the recovery period, but did not identify a confirmed mechanism or actor. Name, domain and legal-name claim searches found no matching listing. Ransomware involvement and threat-actor attribution remain unresolved.
The reviewed evidence does not establish the entry route, encryption scope, a ransom demand, payment or misuse of the copied information. Anonymous allegations about earlier privacy practices are not verified findings about this incident.
Subsequent litigation does not extend the operational outage. The signed and filed Aug. 3, 2026, court order granted final approval of the settlement in Clausner v. American Multispecialty Group, doing business as Esse Health, case 2622-CC00414. It expressly made no finding of liability or wrongdoing. The administrator’s older proposed-settlement wording does not override that order; the reviewed material does not establish payment distribution or an appeal outcome.

The contemporaneous report described unavailable systems, appointment changes and phone problems while offices continued to see patients.
Named patients described records-transfer difficulties and an April30 appointment canceled because the office could not access records; the provider confirmed an investigation.
The report stated 263601 individuals were being notified and described recovery by June2. It treated ransomware as a possibility, with no named group claiming responsibility.
The signed and filed order granted final settlement approval in case2622-CC00414 without a finding or admission of liability.
The administrator links the April2025 cyberattack to litigation against AmericanMultispecialtyGroup doingbusinessasEsseHealth; its FAQ describes a2525000dollar settlement fund.
Esse Health confirmed April21 unauthorized access and file copying, May13 partial information-sharing restoration, and June2 restoration of phones and primary patient-facing systems.
Signed-in members can report an error, update, or missing source.