Back to Intelligence

UNM Health Cyberattack: Defending Hospital Networks Against Operational Disruption

SA
Security Arsenal Team
November 5, 2026
8 min read

On Monday, October 26, 2025, the University of New Mexico Health System (UNM Health) activated emergency protocols following a significant cybersecurity incident that forced the diversion of ambulances, cancellation of appointments, and temporary closure of clinics. This incident represents the nightmare scenario for healthcare CISOs: a cyber threat severe enough to degrade emergency care delivery and force operational shutdowns across clinical environments.

While UNM Health has not publicly confirmed the specific attack vector, the pattern—sudden operational shutdown, patient diversion, and containment measures—aligns with ransomware or destructive wiper incidents targeting electronic health record (EHR) systems and clinical workstations. For defenders, this serves as a stark reminder that healthcare networks remain high-value targets where availability directly impacts human life. This analysis provides actionable detection and hardening guidance to prevent similar disruptions in your environment.

Technical Analysis

Attack Surface and Impact

Healthcare delivery organizations (HDOs) like UNM Health present unique defensive challenges due to their hybrid IT/OT environments. The attack likely targeted:

  • Clinical Workstations: Windows-based systems running EHR clients (Epic, Cerner, Meditech) that cannot tolerate abrupt reboots or encryption
  • Medical Device Gateways: Systems aggregating telemetry from IoMT devices, often running legacy protocols
  • Active Directory: The primary target for lateral movement enabling domain-wide disruption
  • Backup Infrastructure: Veeam, Commvault, or similar platforms targeted to prevent recovery

The diversion of ambulances suggests degradation of systems supporting emergency department operations, likely including patient tracking, bed management, and potentially PACS (Picture Archiving and Communication Systems). Appointment cancellations indicate disruption to scheduling systems and patient portals.

Likely Attack Chain

Based on historical healthcare incidents and the rapid containment required, the probable attack chain involves:

  1. Initial Access: Phishing, exposed RDP, or compromised vendor credentials
  2. Discovery: Enumeration of domain controllers, EHR database servers, and clinical VLANs
  3. Lateral Movement: SMB/Admin$ shares, RDP, or PSExec to reach high-value targets
  4. Impact: Encryption of clinical data, deletion of backups, or deployment of wipers forcing network isolation

Exploitation Status

While no specific CVE has been attributed to the UNM Health incident, healthcare organizations remain primary targets for ransomware-as-a-service (RaaS) groups including ALPHV/BlackCat, LockBit, and BianLian. These groups specifically time attacks for maximum operational impact, often striking during shift changes or weekends to delay detection.

Detection & Response

Detecting the precursors to healthcare operational disruption requires monitoring for mass encryption behaviors, suspicious administrative tool usage in clinical segments, and rapid SMB enumeration. The following detections are tuned to minimize false positives in hospital environments while catching lateral movement and impact phases.

YAML
---
title: Mass File Encryption on Clinical Workstations
id: 8a9b0c1d-2e3f-4a5b-8c9d-0e1f2a3b4c5d
status: experimental
description: Detects suspicious file modification patterns consistent with ransomware encryption targeting clinical data shares.
references:
  - https://attack.mitre.org/techniques/T1486/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.impact
  - attack.t1486
logsource:
  category: file_event
  product: windows
detection:
  selection:
    Image|endswith:
      - '\wscript.exe'
      - '\cscript.exe'
      - '\powershell.exe'
      - '\rundll32.exe'
      - '\vssadmin.exe'
    TargetFilename|contains:
      - '.encrypted'
      - '.locked'
      - '.crypt'
      - 'DECRYPT_INSTRUCTIONS'
      - 'README_FOR_DECRYPT'
  filter:
    Image|endswith: '\backup.exe'
condition: selection and not filter
falsepositives:
  - Legitimate backup software operations
level: high
---
title: Suspicious Admin Share Access in Clinical VLAN
id: 1b2c3d4e-5f6a-7b8c-9d0e-1f2a3b4c5d6e
status: experimental
description: Detects lateral movement attempts via ADMIN$ or C$ shares from non-management systems to clinical workstations or servers.
references:
  - https://attack.mitre.org/techniques/T1021.002/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.lateral_movement
  - attack.t1021.002
logsource:
  category: network_connection
  product: windows
detection:
  selection:
    DestinationPort: 445
    Image|endswith:
      - '\psexec.exe'
      - '\wmiexec.exe'
      - '\at.exe'
      - '\schtasks.exe'
    DestinationIp|startswith:
      - '10.10.'  # Example clinical VLAN
      - '192.168.100.'  # Example medical device VLAN
  filter:
    SourceIp|startswith: '10.1.1.'  # IT management subnet
condition: selection and not filter
falsepositives:
  - Legitimate administrative activity from management VLANs
level: high
---
title: Volume Shadow Copy Deletion Attempt
id: 6e5d4c3b-2a1f-9e8d-7c6b-5a4f3e2d1c0b
status: experimental
description: Detects deletion of volume shadow copies often performed by ransomware prior to encryption to prevent recovery.
references:
  - https://attack.mitre.org/techniques/T1490/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.impact
  - attack.t1490
logsource:
  category: process_creation
  product: windows
detection:
  selection:
    CommandLine|contains:
      - 'vssadmin delete shadows'
      - 'vssadmin delete shadows /all'
      - 'wmic shadowcopy delete'
      - 'bcdedit /set {default} recoveryenabled no'
falsepositives:
  - Legitimate backup maintenance scripts
level: critical
KQL — Microsoft Sentinel / Defender
// Hunt for lateral movement and encryption preparation in healthcare environments
let ClinicalVLANs = dynamic(["10.10.", "192.168.100."]);
let timeframe = 24h;

// Detect suspicious SMB enumeration from clinical workstations
DeviceNetworkEvents
| where Timestamp > ago(timeframe)
| where RemotePort == 445
| where RemoteIP has_any (ClinicalVLANs)
| where InitiatingProcessFileName in~ ("psexec.exe", "wmic.exe", "powershell.exe", "rundll32.exe")
| where not(InitiatingProcessFolderPath has_any ("c:\\windows\\system32", "c:\\windows\\syswow64"))
| summarize Connections = count(), UniqueTargets = dcount(RemoteIP) by DeviceName, InitiatingProcessFileName, InitiatingProcessCommandLine
| where UniqueTargets > 5
| sort by UniqueTargets desc;

// Detect mass file modifications indicative of encryption
DeviceFileEvents
| where Timestamp > ago(timeframe)
| where FileName has_any (".encrypted", ".locked", "DECRYPT", "README")
| summarize FileMods = count() by DeviceName, FolderPath, InitiatingProcessFileName
| where FileMods > 50
| sort by FileMods desc;

// Detect shadow copy deletion attempts
DeviceProcessEvents
| where Timestamp > ago(timeframe)
| where ProcessCommandLine has_any ("vssadmin delete", "wmic shadowcopy delete", "bcdedit /set")
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName
VQL — Velociraptor
-- Hunt for ransomware precursors and lateral movement artifacts in healthcare environments
-- Target clinical workstations and servers for suspicious process execution

-- Detect suspicious SMB admin share access patterns
SELECT Pid, Name, CommandLine, Exe, Username, CreateTime, Netstat.RemoteAddress, Netstat.RemotePort
FROM pslist()
WHERE (CommandLine =~ 'psexec|wmiexec|wmic.*node' 
   OR Name =~ 'vssadmin|bcdedit|diskshadow')
   AND (Netstat.RemotePort == 445 OR Netstat.RemotePort == 3389)

-- Hunt for mass file modifications in user directories (encryption activity)
LET EncryptionHunt = SELECT FullPath, Size, Mtime, Ctime 
FROM glob(globs='C:/Users/*/Desktop/*', accessor='ntfs')
WHERE Mtime > now() - 86400  // Last 24 hours
   AND (FullPath =~ '.encrypted|.locked|.crypt' 
        OR FullPath =~ 'DECRYPT|README')

-- Check for shadow copy deletion artifacts
LET ShadowCopyCheck = SELECT * FROM wmi(
    namespace='root\\cimv2',
    query='SELECT * FROM Win32_ShadowCopy'
)

SELECT * FROM foreach(row=EncryptionHunt, query={
    SELECT FullPath, Size, Mtime, 
           ShadowCopyCheck.ID as ShadowID,
           ShadowCopyCheck.InstallDate as ShadowDate
    FROM scope()
})
PowerShell
# UNM Health Incident - Clinical Workstation Hardening Script
# Run on clinical workstations and EHR gateway servers to verify protections
# Requires administrative privileges

Write-Host "=== UNM Health Defense Verification Script ===" -ForegroundColor Cyan
Write-Host "Checking ransomware protections on: $env:COMPUTERNAME" -ForegroundColor Yellow

# 1. Verify Windows Defender Exploit Guard settings
Write-Host "`n[1] Checking Exploit Guard protections..." -ForegroundColor Green
$exploitProtection = Get-MpPreference | Select-Object -ExpandProperty AttackSurfaceReductionRules_Ids
if ($exploitProtection) {
    Write-Host "ASR Rules Configured: $($exploitProtection.Count)" -ForegroundColor Green
} else {
    Write-Host "WARNING: No ASR rules detected. Enable ransomware protection." -ForegroundColor Red
}

# 2. Check SMBv1 status (must be disabled)
Write-Host "`n[2] Checking SMBv1 status..." -ForegroundColor Green
$smbv1 = Get-SmbServerConfiguration | Select-Object EnableSMB1Protocol
if ($smbv1.EnableSMB1Protocol -eq $false) {
    Write-Host "SMBv1 is DISABLED (Secure)" -ForegroundColor Green
} else {
    Write-Host "CRITICAL: SMBv1 is ENABLED. Disable immediately." -ForegroundColor Red
    Write-Host "Run: Set-SmbServerConfiguration -EnableSMB1Protocol `$false -Force" -ForegroundColor Yellow
}

# 3. Verify Shadow Copies exist and are protected
Write-Host "`n[3] Checking Volume Shadow Copies..." -ForegroundColor Green
$shadows = vssadmin list shadows 2>$null
if ($shadows) {
    $shadowCount = ($shadows | Select-String "Shadow Copy ID").Count
    Write-Host "Shadow copies available: $shadowCount" -ForegroundColor Green
} else {
    Write-Host "WARNING: No shadow copies detected. Verify backup system is operational." -ForegroundColor Yellow
}

# 4. Check for suspicious persistence mechanisms
Write-Host "`n[4] Scanning for suspicious persistence..." -ForegroundColor Green
$runKeys = Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Run" -ErrorAction SilentlyContinue
$suspicious = $runKeys.PSObject.Properties | Where-Object { 
    $_.Value -match "temp|appdata|public|programdata" -and 
    $_.Value -notmatch "OneDrive|Teams|Zoom" 
}
if ($suspicious) {
    Write-Host "Suspicious autoruns detected:" -ForegroundColor Red
    $suspicious | Format-Table Name, Value
} else {
    Write-Host "No obvious suspicious autoruns detected." -ForegroundColor Green
}

# 5. Verify network isolation settings for clinical VLANs
Write-Host "`n[5] Checking Windows Firewall status..." -ForegroundColor Green
$firewall = Get-NetFirewallProfile | Select-Object Name, Enabled
$firewall | Format-Table

# 6. Check RDP NLA requirement
Write-Host "`n[6] Checking RDP Network Level Authentication..." -ForegroundColor Green
$nla = Get-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name "UserAuthentication" -ErrorAction SilentlyContinue
if ($nla.UserAuthentication -eq 1) {
    Write-Host "RDP NLA is ENABLED (Secure)" -ForegroundColor Green
} else {
    Write-Host "WARNING: RDP NLA is DISABLED. Enable to prevent brute force." -ForegroundColor Yellow
}

Write-Host "`n=== Verification Complete ===" -ForegroundColor Cyan
Write-Host "Review any RED flags immediately. Report suspicious findings to your SOC." -ForegroundColor Yellow

Remediation

If your organization experiences a similar incident, immediate actions include:

  1. Network Segmentation: Immediately isolate clinical VLANs from administrative networks. UNM Health's ability to divert patients suggests segmentation prevented total hospital shutdown—verify your segmentation allows life-critical systems to operate independently.

  2. Backup Verification: Ensure offline, immutable backups exist for EHR databases and PACS systems. Test restoration quarterly. UNM Health's incident underscores that backups are the difference between inconvenience and catastrophe.

  3. Disable Legacy Protocols: Disable SMBv1, NetBIOS, and LLMNR across clinical environments. These protocols enable rapid lateral movement and are rarely required for modern medical devices.

  4. Application Allowlisting: Deploy application control (WDAC/AppLocker) on clinical workstations to prevent unauthorized executables. Medical workstations should run only approved EHR clients and clinical applications.

  5. Emergency Access Protocols: Document and test procedures for operating without IT systems. UNM Health's ability to continue emergency care during diversion indicates pre-planned downtime procedures—ensure yours are current and include paper charting workflows.

  6. Vendor Risk Management: Many healthcare incidents originate from third-party vendors. Enforce strict access controls and monitoring for vendor connections to clinical networks.

Category

healthcare

Tags

unm-health, healthcare-security, ransomware, incident-response, hospital-it, clinical-workstations

Related Resources

Security Arsenal Healthcare Cybersecurity AlertMonitor Platform Book a SOC Assessment healthcare Intel Hub

Is your security operations ready?

Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.