The U.S. Cybersecurity and Infrastructure Security Agency (CISA), the Federal Bureau of Investigation (FBI), and the U.S. Secret Service (USSS) — alongside international cybersecurity partners — have released a joint #StopRansomware advisory on the SafePay ransomware group, a rapidly growing encryption-and-extortion operation that has emerged as one of the more aggressive ransomware brands targeting organizations in the healthcare and public health (HPH) sector and other critical infrastructure verticals.
When four federal agencies put their names on a single advisory, that is a signal, not noise. It means the threat has reached a volume, victim profile, and impact threshold that warrants coordinated government response. For HIPAA-covered entities — hospitals, clinics, business associates holding ePHI — a SafePay intrusion is not just an operational outage; it is a reportable breach event with OCR implications, potential regulatory exposure, and patient-safety risk.
This post breaks down what defenders need to know: how SafePay operates, what to hunt for, and exactly what to harden this week.
Technical Analysis: How SafePay Operates
Group Profile
SafePay is a relatively young ransomware operation that first surfaced in late 2024 and scaled aggressively through 2025 and into 2026. Consistent with the modern ransomware-as-a-service ecosystem, SafePay employs a double-extortion model: data is exfiltrated before encryption, and victims are threatened with public leak-site disclosure if payment is not made. The group has claimed a high volume of victims in a short window, with healthcare organizations disproportionately represented — a pattern that has drawn HHS and federal law enforcement attention.
Initial Access
Per the federal advisory and observed incident patterns, SafePay affiliates gain initial access primarily through:
- Compromised or brute-forced VPN and RDP credentials — particularly perimeter remote-access services lacking phishing-resistant MFA
- Exposed remote access infrastructure purchased from initial access brokers (IABs)
- Password-spraying and credential reuse against internet-facing authentication portals
This is important: SafePay is not, per the advisory, defined by a novel zero-day. It is defined by opportunistic exploitation of weak identity and perimeter hygiene. That makes it highly preventable — and highly detectable if your telemetry is in order.
Execution, Defense Evasion, and Impact
Once inside, SafePay operators follow a familiar but ruthlessly efficient playbook:
- Discovery and lateral movement — enumeration of domain assets, SMB/RDP movement to high-value servers (file shares, backup infrastructure, EHR-adjacent systems).
- Defense evasion — attempts to disable or impair endpoint protection and delete recovery options, most notably Volume Shadow Copies via
vssadmin,wmic, orbcdedit-based recovery disabling. - Collection and exfiltration — staging of sensitive data (patient records, financials, HR data) and exfiltration over legitimate channels such as RDP-clipped transfers, cloud sync tools, or FTP clients like FileZilla, often using archiving utilities such as WinRAR/7-Zip to package data.
- Encryption — mass file encryption with a
.safepayextension appended to victim files, and deployment of a ransom note commonly namedreadme_safepay.txtin encrypted directories.
Exploitation Status
This is confirmed active, in-the-wild exploitation at scale. The joint advisory itself is the confirmation. SafePay is not theoretical, not proof-of-concept, and not dormant. The advisory exists because victim counts — including healthcare entities — demanded it.
Detection & Response
The detections below target SafePay's most consistent observable behaviors: shadow copy destruction, recovery tampering, mass .safepay renames, and ransom note artifacts. These are high-fidelity signals — legitimate shadow copy deletion by admins happens, but combined with mass file renames, it is ransomware until proven otherwise.
Sigma Rules
---
title: Shadow Copy Deletion via vssadmin wmic or PowerShell
description: Detects deletion of Volume Shadow Copies, a hallmark ransomware defense-evasion step observed in SafePay intrusions prior to encryption.
references:
- https://www.cisa.gov/stopransomware
- https://attack.mitre.org/techniques/T1490/
author: Security Arsenal
date: 2026/01/15
status: experimental
logsource:
category: process_creation
product: windows
detection:
selection_img:
Image|endswith:
- '\vssadmin.exe'
- '\wmic.exe'
- '\powershell.exe'
- '\pwsh.exe'
selection_cli:
CommandLine|contains:
- 'delete shadows'
- 'shadowcopy delete'
- 'resize shadowstorage'
- 'Delete-WmiObject'
- 'Get-WmiObject Win32_Shadowcopy'
condition: selection_img and selection_cli
falsepositives:
- Backup administrators performing legitimate shadow copy maintenance
- Some backup software performs shadow storage resizing
tags:
- attack.impact
- attack.t1490
level: high
---
title: Boot Recovery Tampering via bcdedit
description: Detects bcdedit commands disabling Windows recovery mode or ignoring boot failures, consistent with SafePay ransomware pre-encryption system preparation.
references:
- https://www.cisa.gov/stopransomware
- https://attack.mitre.org/techniques/T1490/
author: Security Arsenal
date: 2026/01/15
status: experimental
logsource:
category: process_creation
product: windows
detection:
selection:
Image|endswith: '\bcdedit.exe'
CommandLine|contains:
- 'recoveryenabled no'
- 'bootstatuspolicy ignoreallfailures'
falsepositives:
- Rare; some OEM imaging and kiosk configurations
tags:
- attack.impact
- attack.t1490
level: high
---
title: SafePay Ransom Note or Encrypted File Artifact Creation
description: Detects creation of SafePay ransom notes (readme_safepay.txt) or files with the .safepay encrypted extension being written to disk.
references:
- https://www.cisa.gov/stopransomware
- https://attack.mitre.org/techniques/T1486/
author: Security Arsenal
date: 2026/01/15
status: experimental
logsource:
category: file_event
product: windows
detection:
selection_note:
TargetFilename|endswith: '\readme_safepay.txt'
selection_ext:
TargetFilename|endswith: '.safepay'
condition: 1 of selection_*
falsepositives:
- Threat research or sandbox detonation environments
tags:
- attack.impact
- attack.t1486
level: critical
KQL — Microsoft Sentinel / Defender Hunt
This query correlates pre-encryption defense-evasion activity with mass file-renames to the SafePay extension on the same device within a short window — the strongest single signal of an active encryption event.
// Hunt 1: Pre-encryption tampering (shadow copy deletion / recovery disable)
let TamperEvents = DeviceProcessEvents
| where TimeGenerated > ago(7d)
| where (FileName =~ "vssadmin.exe" and ProcessCommandLine has "delete shadows")
or (FileName =~ "wmic.exe" and ProcessCommandLine has "shadowcopy")
or (FileName =~ "bcdedit.exe" and ProcessCommandLine has_any ("recoveryenabled no", "ignoreallfailures"))
| project TamperTime=TimeGenerated, DeviceName, AccountName, ProcessCommandLine, InitiatingProcessFileName;
// Hunt 2: Mass rename to .safepay extension (Defender file events)
DeviceFileEvents
| where TimeGenerated > ago(7d)
| where ActionType == "FileRenamed" and FileName endswith ".safepay"
| summarize RenameCount = count(), FirstRename = min(TimeGenerated), LastRename = max(TimeGenerated), SampleFiles = make_set(FileName, 10) by DeviceName, InitiatingProcessFileName, InitiatingProcessAccountName
| where RenameCount > 50
| join kind=leftouter TamperEvents on DeviceName
| project DeviceName, RenameCount, FirstRename, LastRename, InitiatingProcessFileName, InitiatingProcessAccountName, TamperTime, ProcessCommandLine, SampleFiles
| sort by RenameCount desc
// Hunt 3: Ransom note drops anywhere in the estate
union DeviceFileEvents, (CommonSecurityLog | where isnotempty(FileName))
| where TimeGenerated > ago(7d)
| where tostring(column_ifexists("FileName", "")) has "readme_safepay"
or tostring(column_ifexists("NewFileName", "")) has "readme_safepay"
| project TimeGenerated, DeviceName = column_ifexists("DeviceName", Computer), ActionType = column_ifexists("ActionType", Activity), FileName, InitiatingProcessFileName, FolderPath
Velociraptor VQL — Endpoint Forensic Hunt
Deploy this as a hunt across your Windows fleet to find both the ransom note artifact and live tampering processes, plus residual .safepay files on file servers.
-- SafePay artifact sweep: ransom notes, encrypted files, and tampering processes
SELECT * FROM foreach(row={
SELECT 'RANSOM_NOTE' AS ArtifactType, FullPath AS Evidence, '' AS Detail
FROM glob(globs='C:/Users/*/Desktop/**/readme_safepay.txt')
}, query={
SELECT ArtifactType, Evidence, Detail FROM source()
})
UNION ALL
SELECT 'TAMPER_PROCESS' AS ArtifactType,
Exe AS Evidence,
format(format='%v | PID=%v | User=%v', args=[CommandLine, Pid, Username]) AS Detail
FROM pslist()
WHERE CommandLine =~ '(?i)(delete shadows|shadowcopy delete|recoveryenabled no|ignoreallfailures)'
UNION ALL
SELECT 'PERSISTENCE_CHECK' AS ArtifactType,
Name AS Evidence,
format(format='%v -> %v', args=[Exe, CommandLine]) AS Detail
FROM pslist()
WHERE Exe =~ '(?i)(users\\public|appdata\\local\\temp|programdata)'
AND CommandLine =~ '(?i)(\\.safepay|readme_safepay)'
Remediation / Hardening Script
Run this on critical Windows servers (file servers, backup infrastructure) to verify ransomware resilience controls: shadow copy protection status, RDP exposure, and SMBv1 — three of the most common gaps SafePay-style intrusions exploit.
# Security Arsenal - SafePay Ransomware Resilience Audit (run elevated)
# 1. Verify Volume Shadow Copies exist and vssadmin service is operational
Write-Host '=== Shadow Copy Status ===' -ForegroundColor Cyan
$shadows = Get-WmiObject Win32_ShadowCopy -ErrorAction SilentlyContinue
if ($shadows) { $shadows | Select-Object DeviceObject, InstallDate | Format-Table } else { Write-Warning 'NO shadow copies found - recovery capability degraded. Create a baseline: vssadmin create shadow /for=C:' }
# 2. Check RDP exposure - SafePay initial access vector
Write-Host '=== RDP Configuration ===' -ForegroundColor Cyan
$rdp = Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server' -Name fDenyTSConnections
if ($rdp.fDenyTSConnections -eq 0) { Write-Warning 'RDP ENABLED. Confirm it is NOT internet-exposed and is behind VPN + MFA. To disable: Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server" -Name fDenyTSConnections -Value 1' } else { Write-Host 'RDP disabled - good.' }
$nla = Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name UserAuthentication -ErrorAction SilentlyContinue
if ($nla.UserAuthentication -ne 1) { Write-Warning 'NLA not enforced on RDP. Set UserAuthentication=1' }
# 3. Disable SMBv1 (lateral movement hardening)
Write-Host '=== SMBv1 Status ===' -ForegroundColor Cyan
$smb1 = Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol -ErrorAction SilentlyContinue
if ($smb1.State -eq 'Enabled') { Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol -NoRestart; Write-Host 'SMBv1 disabled (reboot required).' } else { Write-Host 'SMBv1 not enabled - good.' }
# 4. Audit recent vssadmin/bcdedit execution via process creation (4688) if enabled
Write-Host '=== Recent Tampering Events (last 7 days, 4688 required) ===' -ForegroundColor Cyan
Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4688; StartTime=(Get-Date).AddDays(-7)} -ErrorAction SilentlyContinue |
Where-Object { $_.Message -match 'delete shadows|shadowcopy delete|recoveryenabled no|readme_safepay|\.safepay' } |
Select-Object TimeCreated, @{N='Command';E={($_.Message -split "`n") -match 'Process Command Line'}} | Format-List
# 5. Verify Windows Defender Tamper Protection state
Write-Host '=== Defender Tamper Protection ===' -ForegroundColor Cyan
$mp = Get-MpComputerStatus
if (-not $mp.IsTamperProtected) { Write-Warning 'Tamper Protection OFF - ransomware can disable Defender. Enable in MDE/Intune portal.' } else { Write-Host 'Tamper Protection ON.' }
Remediation and Hardening Priorities
There is no single patch for SafePay — the fix is closing the access and resilience gaps its affiliates exploit. Prioritize in this order:
- MFA on every remote access path — no exceptions. VPN, RDP gateways, and any federated SSO portal must enforce phishing-resistant MFA. SafePay's primary entry vector is valid credentials against unauthenticated-perimeter services. This single control breaks the majority of intrusions.
- Eliminate internet-exposed RDP. Audit your external attack surface today (Shodan/Censys your own ranges). RDP belongs behind a VPN or ZTNA broker, full stop.
- Protect your backups from the operator, not just the malware. Immutable/offline backups with separate credentials, and verify restoration quarterly. Shadow copy deletion is step one of the encryption sequence — your backups must survive an authenticated domain admin-level intruder.
- Deploy the detections above. The Sigma rules and KQL hunt give you coverage of the tamper-then-encrypt sequence. Wire the file-rename hunt to a high-severity analytic rule with automatic device isolation via MDE.
- Harden lateral movement paths. Disable SMBv1, tier your admin model, restrict RDP to jump hosts, and alert on new local admin creation and unusual SMB write patterns to ADMIN$/C$ shares.
- Pressure-test your IR plan for double extortion. Decide now, before an incident, who makes the call on payment, who contacts FBI/CISA/USSS, and how you handle the HIPAA Breach Notification Rule clock (60 days to HHS/individuals for 500+ record breaches) if ePHI exfiltration is confirmed.
- Report incidents. The advisory exists because victims reported. CISA (report@cisa.gov), your local FBI field office, and USSS field offices want early notification — and federal engagement materially improves outcomes on decryption keys and actor disruption.
Review the full joint advisory at cisa.gov/stopransomware for the authoritative IOC and TTP listing, and validate your controls against CIS Controls v8 (particularly Controls 4, 6, 11, and 12) and the NIST CSF 2.0 Protect and Respond functions.
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.