Back to Intelligence

Ransomware in Healthcare: Q3 2026 Saw 100 Disclosed Encryption Attacks — Detection and Hardening Guide

SA
Security Arsenal Team
November 20, 2026
10 min read

The HIPAA Journal's Q3 2026 ransomware report paints a picture that anyone defending a hospital, clinic network, or business associate needs to internalize immediately: 100 encryption-based cyber incidents were publicly disclosed against the healthcare sector in Q3 alone. Sector-wide, ransomware groups claimed 353 disclosed attacks in the same quarter — and researchers tracked an estimated 2,668 undisclosed attacks, a 20% increase over prior tracking. For every incident that makes the news, roughly seven never do.

That last number is the one that should keep CISOs up at night. Disclosed attacks represent the visible tip of the iceberg — the organizations that either had a regulatory obligation to report (HIPAA breach notification at 500+ records), paid and got burned anyway, or suffered operational disruption too severe to hide. The 2,668 undisclosed attacks represent victims who paid quietly, contained the incident below reporting thresholds, or haven't yet discovered the full scope of the compromise.

Healthcare remains the top target for encryption-based extortion for three structural reasons: (1) patient safety pressure creates extreme willingness to pay, (2) PHI commands premium resale value on criminal markets, and (3) sprawling, heterogeneous environments — legacy Windows, biomedical devices, flat networks — make consistent hardening genuinely hard. None of those are excuses. This post is about what you can actually do about it.

How These Attacks Actually Play Out

While ransomware families rotate (the affiliates rebrand faster than most organizations patch), the attack chain in 2026 healthcare intrusions remains remarkably consistent. As defenders, we get to pick our interception points:

  1. Initial access — Phishing with credential harvesting, exploitation of internet-facing remote services (VPN concentrators, RDP gateways, third-party remote access tools used by medical device vendors), and purchased access from initial access brokers (IABs).
  2. Persistence and privilege escalation — Valid accounts are the dominant technique. Attackers blend in using stolen credentials, then escalate via misconfigured service accounts, kerberoastable SPNs, or unpatched domain controllers.
  3. Discovery and lateral movement — net.exe, nltest, BloodHound/SharpHound collection, RDP and SMB/ADMIN$ pivoting. This phase often lasts days to weeks.
  4. Defense evasion and staging — Disabling EDR via BYOVD (bring-your-own-vulnerable-driver) tools, deleting Volume Shadow Copies with vssadmin or wmic, clearing event logs, and staging encryption binaries in C:\ProgramData or user temp paths.
  5. Impact — Mass encryption (MITRE ATT&CK T1486) often detonated via Group Policy or PsExec across the domain simultaneously, typically during off-hours weekends to maximize dwell time before detection.

The critical defensive insight: the encryption event is the end of the chain, not the beginning. If your first alert fires when file extensions start changing, you've already lost. Every pre-encryption behavior above is detectable with commodity telemetry.

Exploitation Status

This is not a theoretical threat. These are confirmed, active, in-the-wild campaigns producing hundreds of victim organizations per quarter against healthcare specifically. Ransomware TTPs featured in these campaigns appear repeatedly in CISA KEV-adjacent advisories and joint CISA/HHS HC3 sector alerts. Treat every detection below as production-relevant today.

Detection & Response

Sigma Rules

The following rules target the highest-signal pre-encryption behaviors observed across healthcare ransomware intrusions. Deploy in your SIEM and tune against your administrative tooling baselines — but do not let tuning become an excuse to never enable them.

YAML
---
title: Shadow Copy Deletion via vssadmin or wmic
id: 3f8c2a1e-7b4d-4f9e-a2c6-8d1e5b9a0f31
status: experimental
description: Detects deletion of Volume Shadow Copies, a near-universal pre-encryption step in ransomware intrusions targeting healthcare environments.
references:
  - https://attack.mitre.org/techniques/T1490/
  - https://www.hipaajournal.com/q3-2026-ransomware-report-healthcare/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.impact
  - attack.t1490
logsource:
  category: process_creation
  product: windows
detection:
  selection_img:
    Image|endswith:
      - '\vssadmin.exe'
      - '\wmic.exe'
  selection_cmd:
    CommandLine|contains:
      - 'delete shadows'
      - 'shadowcopy delete'
      - 'resize shadowstorage'
  condition: selection_img and selection_cmd
falsepositives:
  - Backup administrators performing legitimate shadow storage maintenance (rare and schedulable)
level: high
---
title: Mass File Rename Indicative of Ransomware Encryption
id: 9a1d4e72-3c6b-4a8f-b5d2-7e0f1c8a2d44
status: experimental
description: Detects high-velocity file rename/write operations on a single host consistent with ransomware mass encryption activity.
references:
  - https://attack.mitre.org/techniques/T1486/
  - https://www.hipaajournal.com/q3-2026-ransomware-report-healthcare/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.impact
  - attack.t1486
logsource:
  category: file_rename
  product: windows
detection:
  selection:
    TargetFilename|contains:
      - '.locked'
      - '.encrypted'
      - '.crypted'
      - 'RECOVER'
      - 'DECRYPT'
      - 'HOW_TO'
      - 'README_RESTORE'
  condition: selection
falsepositives:
  - Rare; legitimate software does not drop ransom-note-style filenames. Pair with host-level rename velocity thresholds in your SIEM correlation layer.
level: critical
---
title: Ransomware Staging in ProgramData or Public User Directories
id: 5b7e0c39-2f4a-4d1c-9e8b-6a3f7d0c1e55
status: experimental
description: Detects execution of unsigned or uncommon binaries from directories frequently used by ransomware operators to stage encryption payloads before domain-wide detonation.
references:
  - https://attack.mitre.org/techniques/T1074/
  - https://www.hipaajournal.com/q3-2026-ransomware-report-healthcare/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.execution
  - attack.t1074.001
logsource:
  category: process_creation
  product: windows
detection:
  selection:
    Image|startswith:
      - 'C:\ProgramData\'
      - 'C:\Users\Public\'
      - 'C:\Windows\Temp\'
  filter_legit:
    Image|endswith:
      - '\Microsoft\'
      - '\Packages\'
  condition: selection and not filter_legit
falsepositives:
  - Software distribution tools (SCCM, PDQ, RMM agents) executing from temp paths — baseline your RMM tooling and exclude by signer
level: high

KQL — Microsoft Sentinel / Defender

This hunt query surfaces the convergence of pre-encryption behaviors on a single device within a short window — shadow copy deletion, suspicious staging execution, and bcdedit recovery tampering. A single host exhibiting two or more of these behaviors in 24 hours warrants immediate IR escalation. Run it across your fleet, prioritizing clinical VLANs and servers hosting EHR databases.

KQL — Microsoft Sentinel / Defender
let Lookback = 24h;
let ShadowCopy =
    DeviceProcessEvents
    | where TimeGenerated > ago(Lookback)
    | where FileName in~ ("vssadmin.exe", "wmic.exe")
    | where ProcessCommandLine has_any ("delete shadows", "shadowcopy delete", "resize shadowstorage")
    | summarize ShadowEvents = count(), LastSeen = max(TimeGenerated) by DeviceName, Behavior = "ShadowCopyDeletion";
let RecoveryTamper =
    DeviceProcessEvents
    | where TimeGenerated > ago(Lookback)
    | where FileName =~ "bcdedit.exe"
    | where ProcessCommandLine has_all ("recoveryenabled", "no")
    | summarize RecoveryEvents = count(), LastSeen2 = max(TimeGenerated) by DeviceName, Behavior2 = "RecoveryTampering";
let SuspiciousStaging =
    DeviceProcessEvents
    | where TimeGenerated > ago(Lookback)
    | where FolderPath has_any (@"C:\ProgramData\", @"C:\Users\Public\", @"C:\Windows\Temp\")
    | where not(FolderPath has_any (@"\Microsoft\", @"\Packages\"))
    | summarize StagingEvents = count(), SampleProcs = make_set(FileName, 10) by DeviceName;
ShadowCopy
| join kind=fullouter RecoveryTamper on DeviceName
| join kind=fullouter SuspiciousStaging on DeviceName
| extend RiskScore = (todouble(coalesce(ShadowEvents, 0)) * 3) + (todouble(coalesce(RecoveryEvents, 0)) * 2) + todouble(coalesce(StagingEvents, 0))
| where RiskScore >= 3
| project DeviceName, Behavior, ShadowEvents, Behavior2, RecoveryEvents, StagingEvents, SampleProcs, RiskScore
| order by RiskScore desc

Velociraptor VQL

For DFIR teams doing proactive hunts or post-alert triage, this artifact enumerates running processes executing from ransomware staging directories and captures command lines — ideal for rapidly scoping whether a suspect host is actively running a staged payload.

VQL — Velociraptor
-- Hunt: Processes executing from common ransomware staging directories
SELECT Pid, Ppid, Name, Exe, CommandLine, Username, CreateTime
FROM pslist()
WHERE Exe =~ '(?i)(ProgramData|Users\\\\Public|Windows\\\\Temp)'
  AND NOT Exe =~ '(?i)(\\\\Microsoft\\\\|\\\\Packages\\\\)'
ORDER BY CreateTime DESC

Hardening Script

The following PowerShell script verifies critical anti-ransomware controls on Windows endpoints and servers: shadow copy availability, Controlled Folder Access status, and SMBv1 (a legacy protocol still present on far too many biomedical-adjacent systems). Run it via your RMM or GPO scheduled task and forward non-compliant results to your CMDB or SIEM watchlist.

PowerShell
# Security Arsenal - Healthcare Ransomware Readiness Check
# Run as SYSTEM or elevated admin. Output non-compliant hosts to log for SIEM ingestion.

$report = [ordered]@{ Hostname = $env:COMPUTERNAME; Timestamp = (Get-Date -Format o) }

# 1. Verify VSS service is not disabled and shadow copies exist
$vss = Get-Service -Name VSS -ErrorAction SilentlyContinue
$shadows = Get-CimInstance Win32_ShadowCopy -ErrorAction SilentlyContinue
$report.VSSServiceState  = if ($vss) { $vss.StartType } else { "MISSING" }
$report.ShadowCopyCount  = if ($shadows) { $shadows.Count } else { 0 }
$report.VSSCompliant     = ($vss -and $vss.StartType -ne 'Disabled')

# 2. Enable Windows Defender Controlled Folder Access (blocks unauthorized encryptors)
try {
    Set-MpPreference -EnableControlledFolderAccess Enabled -ErrorAction Stop
    $report.ControlledFolderAccess = (Get-MpPreference).EnableControlledFolderAccess
} catch { $report.ControlledFolderAccess = "FAILED_TO_SET" }

# 3. Ensure real-time protection and cloud-delivered protection are enabled
$mp = Get-MpComputerStatus
$report.RealTimeProtection = $mp.RealTimeProtectionEnabled
$report.CloudProtection    = $mp.MAPSReporting

# 4. Disable SMBv1 if present (common on legacy clinical networks)
$smb1 = Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol -ErrorAction SilentlyContinue
if ($smb1 -and $smb1.State -eq 'Enabled') {
    Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol -NoRestart -ErrorAction SilentlyContinue
    $report.SMBv1Action = "DISABLED"
} else { $report.SMBv1Action = "NotPresentOrAlreadyDisabled" }

# 5. Audit: alert on shadow copy deletion attempts going forward
auditpol /set /subcategory:"Security System Extension" /success:enable /failure:enable | Out-Null

# Emit as single-line JSON for log forwarder pickup
$report | ConvertTo-Json -Compress | Out-File -Append "C:\ProgramData\SecArsenal\ransomware_readiness.jsonl"
Write-Output ($report | ConvertTo-Json -Compress)

Remediation and Strategic Priorities

If you take nothing else from the Q3 2026 data, take this: the attackers' economics depend on your recovery being harder than paying. Break that equation.

  1. Immutable, tested backups. Maintain at least one offline or immutable backup copy (object-lock, WORM storage, or physically isolated) of EHR databases, PACS archives, and domain controller system state. Then — and this is where most healthcare organizations fail — test restoration quarterly. A backup you've never restored is a hypothesis, not a control. Measure your actual RTO against clinical downtime tolerances.

  2. Segment the clinical network. Flat networks are why a compromised billing workstation becomes an encrypted radiology archive. Enforce VLAN/ACL separation between biomedical devices, clinical workstations, administrative systems, and server infrastructure. Block workstation-to-workstation SMB/RDP entirely — there is almost never a legitimate need, and it kills PsExec-style detonation.

  3. Kill shadow copy tampering as a technique. Alert on the Sigma rule above, restrict vssadmin and wmic execution via AppLocker or WDAC to admin-only paths, and consider redirecting restore points to protected storage ransomware cannot reach.

  4. Harden identity. Phishing-resistant MFA (FIDO2) on all remote access — VPN, RDP gateways, vendor remote support tools, and cloud admin portals. Audit kerberoastable service accounts and enforce gMSA or 25+ character randomized passwords. The majority of these intrusions start with valid accounts, not exploits.

  5. Protect the EDR you paid for. BYOVD attacks specifically target security tooling. Enable tamper protection, monitor for EDR service stops and sensor heartbeats going silent (a fleet-wide sensor gap during off-hours is itself a critical alert), and restrict driver installation to administrators.

  6. Know your HIPAA breach obligations before you need them. Incidents affecting 500+ individuals trigger HHS OCR notification within 60 days, and state attorneys general timelines are often shorter. Pre-stage your IR retainer, legal counsel, and communications plan. The organizations that disclosed 100 attacks this quarter mostly did so under duress — the 2,668 that didn't disclose are one OCR audit away from compounding the damage.

  7. Monitor the ecosystem, not just your perimeter. Third-party and business associate compromises are a growing share of healthcare encryption incidents. Inventory every vendor with network access or PHI custody, and hold them to your segmentation and MFA standards contractually.

The Q3 trend line — 20% growth in undisclosed attacks — means the adversary's operational tempo is increasing while disclosure visibility stays flat. Defenders cannot wait for the next quarterly report to validate their posture. Deploy the detections, run the readiness checks, and test your restore path this week.

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.