
The University of New Mexico Health System disclosed a cybersecurity incident on October 26 that forced it to divert ambulance traffic, cancel appointments across more than 30 clinics, and close parts of the University of New Mexico Health Sciences Center.
That operational impact matters even before investigators can say whether patient records were accessed. UNM operates New Mexico's only Level 1 trauma center, so taking clinical systems offline immediately became a patient-safety and regional-capacity problem, not merely an IT outage.
UNM Health said its security teams were working to resolve a cybersecurity issue affecting the Health Sciences Center. Its initial notice told patients not to report to facilities, directed emergencies to 911, and said non-emergency care should be delayed. The university also sent non-essential personnel and students home.
The Associated Press reported that operations began resuming in phases later that day, while the incident remained under investigation. The FBI said it was assisting a partner agency. UNM has not publicly confirmed the attack method, the identity of an actor, or whether patient data was accessed.
That distinction is important. Employee reports and media accounts described messages claiming that student, employee, and patient information had been stolen, but those claims are not a substitute for forensic confirmation. Healthcare organizations should communicate what is known, what is being investigated, and what patients should do without turning an allegation into a confirmed data breach.
Hospitals cannot simply switch off every connected system and continue normally. Clinical records, imaging, laboratory workflows, medication access, identity services, communications, building controls, and scheduling systems are interdependent. A defensive shutdown can therefore produce the same immediate symptom as an attack: slower care and reduced capacity.
The incident is a reminder that incident response in healthcare must include clinical continuity. A technically successful containment step is incomplete if clinicians do not have tested paper procedures, trusted downtime forms, alternate communications, and a safe process for reconciling records after systems return.
Healthcare security teams should treat this as a live investigation rather than wait for a public attribution:
The UNM disruption demonstrates why hospital resilience cannot be measured only by whether malware is removed. The more consequential question is whether care can continue safely while the organization determines what happened. In healthcare, recovery planning is part of cybersecurity—not a separate business-continuity exercise.
Written by
Research
A DevOps engineer and cybersecurity enthusiast with a passion for uncovering the latest in zero-day exploits, automation, and emerging tech. I write to share real-world insights from the trenches of IT and security, aiming to make complex topics more accessible and actionable. Whether I’m building tools, tracking threat actors, or experimenting with AI workflows, I’m always exploring new ways to stay one step ahead in today’s fast-moving digital landscape.
Get the latest cybersecurity insights delivered to your inbox.