Healthcare Data Breach Disclosures and Litigation Affecting Hundreds of Thousands of Patients
Bell Ambulance reported that a February 2025 network intrusion led to the compromise of protected health information for 237,830 individuals, after unauthorized activity was detected on Feb. 13, 2025. The organization said the exposed data can include names, dates of birth, Social Security numbers, driver’s license numbers, financial account information, medical information, and health insurance information; it offered 12–24 months of credit monitoring/identity protection and stated it was not aware of misuse at the time of notification. The incident response included third-party forensic support, and notifications were issued in phases as the data review progressed, with additional letters sent into March 2026.
Separately, Cornerstone Specialty Hospitals agreed to pay $2.35 million to settle a class action lawsuit tied to a data breach that reportedly affected nearly 500,000 individuals. The available reporting focuses on the settlement amount and impacted population size, indicating ongoing legal and financial consequences for large-scale healthcare data exposure even when technical details of the underlying intrusion are not publicly described in the same source.

Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
12 events from the most recent confirmed update back to the earliest known activity.
Cornerstone Specialty Hospitals agrees $2.35M breach settlement
Cornerstone Specialty Hospitals agreed to pay $2.35 million to settle a class action lawsuit tied to a data breach affecting nearly 500,000 individuals. The provided reference does not include further technical details about the underlying incident.
Bell Ambulance notifies consumers reported to Maine AG
Bell Ambulance reported to the Maine Attorney General that written notice to affected consumers was sent on March 9, 2026. The filing said 237,830 people were affected, including 30 Maine residents.
Bell Ambulance completes internal review
Bell Ambulance completed its internal review of the incident on February 20, 2026. The review concluded that 237,830 individuals were affected and clarified the categories of compromised data.
Second Bell Ambulance notification wave issued
Bell Ambulance sent another wave of notifications on January 15, 2026 after identifying more affected individuals. The company continued offering 12 months of free credit monitoring and identity protection.
Bell Ambulance breach discovered in later review
A Maine Attorney General filing states the Bell Ambulance breach was discovered on December 23, 2025. This appears to reflect a later determination or reporting milestone tied to the broader incident review.
Additional Bell Ambulance victims identified in later review
Bell Ambulance identified additional affected individuals through the fall of 2025, expanding the scope of the breach. This led to later notification waves beyond the initial April 2025 notices.
Alexes Hazen practice suffers unauthorized system access
An unauthorized party accessed systems at Alexes Hazen, MD, PLLC between June and July 2025 and may have exfiltrated limited patient data. The practice later reported the incident to HHS OCR with a placeholder count of 500 affected individuals while its review continued.
Northwest Medical Homes identifies cybersecurity incident
Northwest Medical Homes in Oregon identified a cybersecurity incident on May 13, 2025 that may have exposed protected health information. The organization notified law enforcement, but the total number of affected individuals was not yet public.
First Bell Ambulance victim notifications begin
Bell Ambulance began notifying affected individuals in the first wave on April 18, 2025. The company also offered credit monitoring and identity protection services to impacted people.
Bell Ambulance publicly discloses cyberattack
Bell Ambulance publicly disclosed the breach on April 14, 2025, after the Medusa ransomware group claimed responsibility for the attack. Reports said Medusa alleged it stole about 219 GB of data and demanded $400,000.
Bell Ambulance detects unauthorized network activity
Bell Ambulance detected unauthorized activity on its network on February 13, 2025 and began investigating the incident with forensic specialists. The company later determined data had been compromised.
Bell Ambulance network intrusion begins
Attackers gained unauthorized access to Bell Ambulance systems during a breach window later reported as running from February 7 to February 14, 2025. Sensitive personal, financial, and health information was exposed during the incident.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
7 references tracked. Mallory keeps watching after this page renders.
Bell Ambulance breach impacts over 237K | brief | SC Media
scworld.com
Open sourceBell Ambulance data breach impacted over 238,000 people
securityaffairs.com
Open sourceBell Ambulance data breach impacted over 238,000 people - DataBreaches.Net
databreaches.net
Open source235,000 affected by cyberattack on largest ambulance provider in Wisconsin | The Record from Recorded Future News
therecord.media
Open sourceFebruary 2025 Cyberattack Affected More Than 230K Bell Ambulance Patients
hipaajournal.com
Open sourceteiss - News - Cornerstone Specialty Hospitals pays $2.35m to settle data breach class action lawsuit
teiss.co.uk
Open sourceOffice of the Maine AG: Consumer Protection: Privacy, Identity Theft and Data Security Breaches
maine.gov
Open sourceSee the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.


