The University of New Mexico Health Sciences Center says its critical electronic systems are back online after a cyberattack interrupted care on October 26. The disruption diverted ambulances, suspended outpatient surgeries and appointments, and canceled health-sciences classes.

Bill Toulas’s October 27 reporting identifies a ransomware group’s claim of responsibility. The university’s October 27, 2:02 p.m. update gives a narrower assessment:

Their assessment determined that the event affected some end-user devices but did not penetrate core systems or servers.

Evidence status: a university-confirmed cyberattack and care disruption; attacker-reported ransomware and data theft. The reviewed sources do not independently verify the claimed theft or the attacker’s asserted reach across the university.

Restored service does not erase the interruption

The university’s notice gives this timeline, in local New Mexico time:

  • October 26, around 11 a.m.: security teams began containment after identifying the threat.
  • 12:30–2:30 p.m.: UNM Health temporarily diverted ambulances to other health systems. Outpatient surgeries and appointments were suspended for the rest of the day.
  • From 2:30 p.m.: teams began restoring operations in phases as they judged it safe.
  • October 27, 2:02 p.m. update: critical electronic systems were back online, hospitals were fully open, ambulance operations were normal and clinics had resumed scheduled care.

UNM says care teams will reschedule affected appointments and procedures. Its notice retains older instructions telling patients to stay away on October 26; those are historical, not its current hospital status.

Health-sciences classes remained canceled on October 27. UNM expected academic and research programs to resume October 28. It says Central and branch-campus classes were unaffected. That is a stated recovery plan, not confirmation that tomorrow’s reopening has already happened.

Attacker claims and device evidence have different limits

BleepingComputer reports that the Byod ransomware group claimed 36,000 systems and broad access to identity infrastructure, databases and personal information. That number is the attacker’s assertion, not an established count of compromised systems or affected people.

Local station KOB’s reporting describes a partial recording of an extortion message reportedly played on employee computers. It also reports altered screens and employee accounts of suspicious computer behavior. KOB explicitly says officials had not confirmed the message’s claims.

A message on an endpoint supports the account of a disruptive intrusion. It cannot, by itself, prove access to every database named in an extortion demand. UNM’s published assessment that core systems were not penetrated is also an institutional finding, not an independently published forensic audit.

The university says it involved external partners and notified state and federal law enforcement. It has not disclosed an entry point, an affected software version, a specific patch or a verified stolen-record inventory.

Practical response starts with current service information

For patients: use the hospital’s known contact channel to confirm a postponed appointment or procedure. Do not rely on an old closure message still quoted in a developing article. In an emergency, call 911, as UNM’s notice advises.

For staff and students: follow current institutional IT and scheduling instructions. Verify unsolicited credential, payment or record requests through an independently opened university channel. The reviewed notice contains no public, universal password-reset order.

For operators of other health systems: the documented response makes continuity planning concrete. Exercise ambulance diversion, alternate clinical communication, an emergency coordination center and staged restoration. Treat those as lessons from the published response, not proof that any particular control caused or prevented this intrusion.

Caveat: The criminal investigation remains active. Neither the ransomware group’s claim nor the return of service settles the full data-exposure question.