Back to Intelligence

Greiz Hospital Ransom Attack: Hardening Clinical Networks Against Intrusions and Rebuilding Critical Emergency Operations

SA
Security Arsenal Team
November 18, 2026
12 min read

The Greiz-Ronneburg district hospital in Thuringia, Germany, is back online after a criminal extortion attack knocked its emergency department offline. The hospital reported a full system failure on Saturday evening, 14 November; by Sunday morning the emergency room was completely out of service, and staff were forced to divert patients and revert to paper-based workflows. The emergency room began a phased reopening on Monday evening, 16 November, following a multi-day recovery effort.

German investigators are probing the intrusion, but as of this reporting no state links have been publicly established. This remains a criminal extortion attack against a healthcare provider that sits at the heart of the regional emergency care system. That classification matters little to the patients whose care was delayed — the operational reality is the same as many high-profile healthcare ransomware incidents: loss of access to the hospital information system (HIS), interruption of the emergency department, and a scramble to keep life-critical services running.

For healthcare CISOs, SOC analysts, and hospital IT leaders, Greiz is a familiar and urgent lesson. These attacks rarely exploit exotic zero-days; they typically succeed through well-known initial access vectors — exposed remote access, compromised credentials, phishing, or vulnerable perimeter services — before moving laterally and encrypting core clinical and administrative systems. The defensive controls, detection telemetry, and hardening steps below are designed for the exact operational pressures hospitals face: 24/7 availability, legacy clinical applications, and a thin margin for downtime in life-safety systems.

Technical Analysis

Affected Organization and Impact

The victim is the district hospital Greiz-Ronneburg (Kreiskrankenhaus Greiz) in the federal state of Thuringia, Germany. It is the primary provider for the Greiz district and surrounding region, operating an emergency room that serves a broad rural catchment area. The attack resulted in a complete failure of central IT systems beginning Saturday, 14 November, with the emergency department fully out of service by Sunday morning. The hospital began reopening its ER on Monday evening, 16 November, indicating a recovery time objective (RTO) of roughly 48–72 hours for that specific function — a metric that should be the upper bound of acceptable for any hospital's critical care services.

No specific ransomware variant has been publicly named, and no CVE has been associated with this intrusion in the available reporting. The extortion-only phrasing ("Erpressungsangriff") indicates the attackers likely exfiltrated data and are threatening publication, a standard double-extortion tactic even when encryption was not the sole objective. Investigators have not attributed the attack to any nation-state actor.

How These Attacks Typically Work (Defender's Perspective)

Healthcare ransomware incidents like Greiz almost universally follow a recognizable intrusion lifecycle. Understanding each stage is essential for building detections that fire before encryption, not after.

1. Initial Access. The most common entry points in European hospital attacks over the past 24 months are:

  • External Remote Services (T1133) — exposed RDP, VPN gateways, or Citrix/VDI portals with weak MFA or unpatched services
  • Phishing (T1566) — malicious attachments or credential-harvesting links targeting administrative and clinical staff
  • Exploit Public-Facing Application (T1190) — unpatched web applications, VPN concentrators, or remote access software

2. Execution and Defense Evasion. Once inside, operators typically deploy legitimate administrative tools (PsExec, PowerShell, WMI) and attempt to disable or blind security controls. Common behaviors include tampering with Windows Defender or third-party EDR, clearing event logs, and disabling Volume Shadow Copies to inhibit recovery.

3. Discovery and Lateral Movement. Attackers map the internal network, identify the hospital information system (HIS), domain controllers, and backup infrastructure. Movement is typically over SMB (445) and RDP (3389) using harvested or cracked credentials.

4. Impact — Encryption and Service Disruption. The final stage is simultaneous mass encryption of servers and endpoints, deletion of backups, and the delivery of ransom notes. In a hospital setting, the most damaging effect is loss of the HIS and PACS, which immediately disables electronic patient records, lab results, medication management, and radiology — forcing the emergency department to close or operate at drastically reduced capacity.

Exploitation Status

No CVE is publicly associated with the Greiz attack at this time, and no specific malware family has been confirmed in the available reporting. The incident is a confirmed, in-the-wild criminal intrusion that resulted in operational disruption. Healthcare security teams should treat the TTPs outlined above as immediately actionable and hunt for them proactively, rather than waiting for a specific IOC to be published.

Detection & Response

The detections below focus on the behaviors most consistently observed in healthcare ransomware intrusions: shadow copy deletion, security tool tampering, suspicious administrative tool execution, and anomalous lateral movement. They are written to be tuned for a hospital environment, not to fire on every administrative action.

Sigma Rules

YAML
---
title: Ransomware Shadow Copy Deletion via vssadmin or wmic
id: 7f2e1a44-9b3c-4d88-a5e1-2c3f8a901234
status: experimental
description: Detects attempts to delete Volume Shadow Copies, a common pre-encryption step in ransomware attacks on hospital servers and endpoints.
references:
  - https://attack.mitre.org/techniques/T1490/
author: Security Arsenal
date: 2026/02/12
tags:
  - attack.impact
  - attack.t1490
logsource:
  category: process_creation
  product: windows
detection:
  selection_img:
    Image|endswith:
      - '\vssadmin.exe'
      - '\wmic.exe'
      - '\bcdedit.exe'
  selection_cmd:
    CommandLine|contains:
      - 'delete shadows'
      - 'shadowcopy delete'
      - 'resize shadowstorage'
      - 'recoveryenabled no'
  condition: selection_img and selection_cmd
falsepositives:
  - Legitimate backup or system administration activity
level: high
---
title: Security Tool Tampering on Clinical Workstations
id: 3c8a5f12-6d7b-4e91-8c2a-9f1b3c5d7e8f
status: experimental
description: Detects attempts to stop, disable, or tamper with Windows Defender and common EDR services, a frequent precursor to ransomware deployment in healthcare environments.
references:
  - https://attack.mitre.org/techniques/T1562.001/
author: Security Arsenal
date: 2026/02/12
tags:
  - attack.defense_evasion
  - attack.t1562.001
logsource:
  category: process_creation
  product: windows
detection:
  selection_img:
    Image|endswith:
      - '\powershell.exe'
      - '\cmd.exe'
      - '\sc.exe'
      - '\net.exe'
  selection_cmd:
    CommandLine|contains:
      - 'Set-MpPreference -DisableRealtimeMonitoring'
      - 'Set-MpPreference -DisableBehaviorMonitoring'
      - 'stop windefend'
      - 'stop sense'
      - 'stop msmpsvc'
      - 'DisableAntiSpyware'
      - 'DisableAntiVirus'
  condition: selection_img and selection_cmd
falsepositives:
  - Rare legitimate administrative troubleshooting
level: high
---
title: PsExec or Remote Service Creation for Lateral Movement
id: 9d1b3e5a-2f4c-4a87-b6d9-1e3f5a7c9d2e
status: experimental
description: Detects execution of PsExec-style remote service installation, commonly used by ransomware operators to move laterally from a beachhead to hospital servers and the HIS.
references:
  - https://attack.mitre.org/techniques/T1569.002/
author: Security Arsenal
date: 2026/02/12
tags:
  - attack.lateral_movement
  - attack.t1021.002
  - attack.t1569.002
logsource:
  category: process_creation
  product: windows
detection:
  selection:
    CommandLine|contains:
      - 'psexec'
      - '\\admin$\\'
      - '\\ipc$\\'
      - '-accepteula'
  filter:
    Image|endswith:
      - '\PsExec.exe'
      - '\PsExec64.exe'
  condition: selection and not filter
falsepositives:
  - Legitimate systems administration in tightly controlled windows
level: medium

KQL Hunt (Microsoft Sentinel / Defender)

This hunt looks for a convergence of high-risk pre-ransomware behaviors on a single host within a short window: shadow copy deletion, Defender tampering, and suspicious administrative tool execution. Run it against endpoints and servers in clinical VLANs, especially domain controllers, HIS/application servers, and backup infrastructure.

KQL — Microsoft Sentinel / Defender
let TimeWindow = 1h;
let HighRiskHosts = dynamic(["DC", "HIS", "PACS", "BACKUP", "SQL"]);
let ShadowCopy =
    DeviceProcessEvents
    | where TimeGenerated > ago(7d)
    | where FileName in~ ("vssadmin.exe", "wmic.exe", "bcdedit.exe")
    | where ProcessCommandLine has_any ("delete shadows", "shadowcopy delete", "resize shadowstorage", "recoveryenabled no")
    | project ShadowTime=TimeGenerated, DeviceName, AccountName, ShadowCmd=ProcessCommandLine;
let DefenderTamper =
    DeviceProcessEvents
    | where TimeGenerated > ago(7d)
    | where FileName in~ ("powershell.exe", "cmd.exe", "sc.exe", "net.exe")
    | where ProcessCommandLine has_any ("Set-MpPreference -DisableRealtimeMonitoring", "Set-MpPreference -DisableBehaviorMonitoring", "stop windefend", "stop sense", "DisableAntiSpyware")
    | project TamperTime=TimeGenerated, DeviceName, AccountName, TamperCmd=ProcessCommandLine;
let LateralTool =
    DeviceProcessEvents
    | where TimeGenerated > ago(7d)
    | where ProcessCommandLine has_any ("psexec", "\\admin$\\", "\\ipc$\\", "-accepteula")
    | where FileName !in~ ("psexec.exe", "psexec64.exe")
    | project LateralTime=TimeGenerated, DeviceName, AccountName, LateralCmd=ProcessCommandLine;
ShadowCopy
| join kind=inner DefenderTamper on DeviceName
| join kind=inner LateralTool on DeviceName
| where ShadowTime between (TamperTime - TimeWindow .. TamperTime + TimeWindow)
| project DeviceName, AccountName, ShadowTime, ShadowCmd, TamperTime, TamperCmd, LateralTime, LateralCmd
| sort by DeviceName asc

Tune HighRiskHosts to your naming convention and adjust the time window to match your environment's normal administrative tempo. The goal is to catch the correlated sequence, not any single event in isolation.

Velociraptor VQL

This artifact hunts for evidence of shadow copy deletion, suspicious service creation, and recent execution of administrative tools across a hospital server fleet. Deploy it against domain controllers, HIS/application servers, and backup servers during a ransomware hunt or post-incident sweep.

VQL — Velociraptor
-- Hunt for ransomware precursor artifacts on Windows servers
SELECT 
    Pid,
    Name,
    Exe,
    CommandLine,
    Username,
    CreateTime
FROM pslist()
WHERE CommandLine =~ '(vssadmin|wmic|bcdedit).*?(delete shadows|shadowcopy delete|recoveryenabled no)'
   OR CommandLine =~ '(sc|net)\s+(stop|config).*?(windefend|sense|msmpsvc|sophos|sentinel)'
   OR CommandLine =~ '(psexec|admin\\$|ipc\\$|-accepteula)'
   OR Exe =~ '(?i)\\\\(psexec|paexec|remcom).*?\\.exe$'

For persistence and artifact collection, pair this with a hunt for recently created services and unexpected files in C:\Windows\Temp, C:\ProgramData, and administrative shares.

Remediation / Hardening Script (PowerShell)

This PowerShell script is designed for hospital Windows servers and clinical workstations. It verifies that critical protections are enabled, confirms shadow copies are configured, checks RDP exposure, and reports on the status of key services. Run it as part of a pre-incident hardening audit or immediately after a suspected intrusion to validate the integrity of the recovery environment.

PowerShell
# Healthcare Ransomware Hardening & Verification Script
# Run elevated on servers and clinical workstations

Write-Host "=== Security Arsenal: Ransomware Hardening Verification ===" -ForegroundColor Cyan

# 1. Verify Windows Defender / EDR is running and tamper protection is on
$defender = Get-MpComputerStatus -ErrorAction SilentlyContinue
if ($defender) {
    Write-Host "[Defender] Real-time Protection: $($defender.RealTimeProtectionEnabled)"
    Write-Host "[Defender] Tamper Protection:   $($defender.IsTamperProtected)"
    Write-Host "[Defender] Behavior Monitoring: $($defender.BehaviorMonitorEnabled)"
    if (-not $defender.RealTimeProtectionEnabled -or -not $defender.IsTamperProtected) {
        Write-Warning "Defender protections are degraded. Investigate and re-enable immediately."
    }
} else {
    Write-Warning "Defender status unavailable. Verify third-party EDR is running."
}

# 2. Enable Tamper Protection (if not already on)
try {
    Set-MpPreference -DisableRealtimeMonitoring $false -ErrorAction Stop
    Set-MpPreference -DisableBehaviorMonitoring $false -ErrorAction Stop
    Write-Host "[OK] Real-time and behavior monitoring enforced." -ForegroundColor Green
} catch {
    Write-Error "Failed to enforce Defender settings: $_"
}

# 3. Verify Volume Shadow Copies are configured and not disabled
$shadowStorage = vssadmin list shadowstorage 2>$null
if ($shadowStorage -match "No items found") {
    Write-Warning "No shadow storage configured. Enabling for system drive."
    vssadmin resize shadowstorage /for=C: /on=C: /maxsize=10%
} else {
    Write-Host "[OK] Shadow copy storage is configured." -ForegroundColor Green
}

# 4. Check for suspicious recent service creation (last 7 days)
Write-Host "`n[+] Recent Service Installations (last 7 days):"
Get-WinEvent -FilterHashtable @{LogName='System'; Id=7045; StartTime=(Get-Date).AddDays(-7)} -ErrorAction SilentlyContinue |
    Select-Object TimeCreated, Message |
    Format-List

# 5. Audit RDP exposure and recommend restriction
$rdpEnabled = Get-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server' -Name 'fDenyTSConnections' -ErrorAction SilentlyContinue
if ($rdpEnabled.fDenyTSConnections -eq 0) {
    Write-Warning "RDP is enabled. Restrict to specific admin VLANs and require MFA/VPN."
} else {
    Write-Host "[OK] RDP is disabled." -ForegroundColor Green
}

# 6. Verify SMBv1 is disabled (common lateral movement vector)
$smb1 = Get-SmbServerConfiguration | Select-Object EnableSMB1Protocol
if ($smb1.EnableSMB1Protocol) {
    Write-Warning "SMBv1 is enabled. Disabling."
    Set-SmbServerConfiguration -EnableSMB1Protocol $false -Force
} else {
    Write-Host "[OK] SMBv1 is disabled." -ForegroundColor Green
}

# 7. Check for open administrative shares from unexpected sources
Write-Host "`n[+] Active Admin Share Connections:"
Get-SmbSession | Where-Object { $_.ShareName -match 'ADMIN\$|C\$|IPC\$' } |
    Select-Object ClientComputerName, ShareName, SessionId |
    Format-Table -AutoSize

Write-Host "`n=== Hardening verification complete. Review warnings above. ===" -ForegroundColor Cyan

Remediation

The Greiz hospital incident did not stem from a single software vulnerability, so remediation is about closing the systemic gaps that allow ransomware to succeed in healthcare environments.

  1. Restore from Clean, Isolated Backups. The hospital's ability to reopen its ER within 72 hours indicates viable backups existed. Verify your backup infrastructure is air-gapped or immutable, and that you have tested restoration of the HIS, PACS, and domain controllers under realistic conditions. Document an RTO of less than 24 hours for life-critical systems and an RPO of less than 1 hour for patient data.

  2. Patch and Harden Remote Access. Close or strictly control all external-facing remote access. If VPN or RDP is required, enforce phishing-resistant MFA (FIDO2), restrict by source IP, and place services behind a zero-trust gateway. Patch all perimeter devices — firewalls, VPN concentrators, and remote access software — on an emergency cadence.

  3. Segment Clinical and Administrative Networks. The emergency department should not share a flat network with general administrative workstations. Implement strict VLAN segmentation, and firewall rules that deny workstation-to-server SMB/RDP except from designated administrative jump hosts. HIS and PACS servers should reside in their own protected segments.

  4. Disable Legacy Protocols and Tools. Turn off SMBv1, restrict PsExec and administrative shares, and block PowerShell remoting from standard user workstations. Use application control (WDAC or AppLocker) to prevent unauthorized binaries from running on clinical devices.

  5. Harden Endpoint and Server Defenses. Ensure EDR is deployed on all clinical workstations and servers with tamper protection enforced. Enable attack surface reduction rules in Microsoft Defender, particularly rules that block Office child processes, script obfuscation, and credential theft from LSASS.

  6. Prepare a Hospital-Specific Incident Response Plan. The plan must include clinical downtime procedures, a communication tree for diverting patients, and pre-negotiated retainers with DFIR and legal counsel. Conduct tabletop exercises that simulate loss of the HIS during a mass-casualty event — the Greiz scenario — and measure how long it takes to restore emergency operations.

  7. Engage with National Healthcare CERTs. German hospitals should maintain contact with the BSI and the relevant state-level health authorities. In the U.S., HHS/HC3 and CISA provide sector-specific alerts and coordination. Report incidents promptly; early engagement accelerates access to decryption tools and threat intelligence.

No vendor patch or CVE-specific mitigation applies here because the attack vector remains unconfirmed. The defensive value is in the fundamentals: tested backups, hardened remote access, network segmentation, and detections that catch the ransomware kill chain before encryption begins.

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.