BREACH WATCH BRIEF High 💀 Ransomware

Byod Ransomware Compromises 36,000 Systems at UNM Health, Disrupting Patient Care and Surgeries

UNM Health confirmed a ransomware attack that forced the suspension of admissions, surgeries, and classes while exposing personal, payroll, and EHR data. The breach highlights the importance of incident‑response controls that generate defensible audit evidence.

SeverityHigh
Type💀 Ransomware
ConfidenceHigh
ReportedOct 27, 2026
Healthcare & Life Sciences Healthcare providers Academic medical centers Organizations using integrated AD/Entra and EHR systems Malware Ransomware

What happened

The University of New Mexico Health Sciences Center suffered a ransomware intrusion attributed to the Byod gang. The attackers reported compromising 36,000 systems, including Active Directory forests, Group Policy, the Microsoft Entra tenant, and two Oracle databases. They posted a data‑leak notice listing stolen SSNs, payroll and student records, internal emails, research data, hospital appointment information, and Cerner EHR rosters. UNM Health limited new admissions, diverted ambulances, and suspended outpatient surgeries while classes were canceled. The gang later offered free decryption keys for healthcare victims but warned it would retain the stolen data.

Why it matters for trust and compliance

  • The incident tests the effectiveness of an organization’s incident‑response control—specifically the ability to detect, contain, and document a ransomware event with evidence that satisfies multiple audit frameworks.
  • Map incident‑response procedures to NIST CSF Detect and Respond functions and capture real‑time logs as audit evidence.
  • Use continuous evidence collection to demonstrate control effectiveness during breach investigations and regulator reporting.

Who is affected

Healthcare providers Academic medical centers Organizations using integrated AD/Entra and EHR systems

Recommended actions

  1. Activate your ransomware response playbook: isolate affected assets, shut down lateral movement, and engage forensic investigators.
  2. Validate that incident‑response controls are mapped to your framework of record and that evidence (logs, snapshots, chain‑of‑custody) is being collected continuously.
  3. Notify regulators and affected individuals per HIPAA breach‑notification requirements and retain all communications for audit readiness.

Regulations library

Every US state privacy law, on one map

24 states have a comprehensive privacy law in the library, alongside the EU, UK, US federal and global laws: 102 in all, each explained in plain words with its sources. Select a state to see what applies there.

  • In force
  • Coming into force
  • Sector laws
AK ME VT NH WA ID MT ND MN IL WI MI NY RI MA OR NV WY SD IA IN OH PA NJ CT CA UT CO NE MO KY WV VA MD DE AZ NM KS AR TN NC SC DC OK LA MS AL GA HI TX FL

Get the Breach Digest

The incidents that matter for your vendors and your data, analysed for practitioners, in one email.