Back to Intelligence

Ryuk Ransomware Operator Sentenced: Detection and Hardening Guide for Ryuk-Style Encryption Attacks

SA
Security Arsenal Team
September 23, 2026
8 min read

A member of the Ryuk ransomware operation has been sentenced to 24 months in federal prison and three years of supervised release after pleading guilty to hacking U.S. companies and deploying encryption against their systems. While the sentencing closes one chapter on one of the most destructive ransomware families of the past decade, the operational reality for defenders has not changed: Ryuk's playbook — mass shadow copy deletion, PsExec-driven lateral movement, and rapid domain-wide encryption — is still in daily use by modern ransomware affiliates operating under different brand names.

Ryuk caused hundreds of millions of dollars in damage across healthcare systems, municipalities, and enterprises. Its operators pioneered the "big game hunting" model that groups like LockBit, Black Basta, and Akira inherited wholesale. If your detection stack was never tuned against Ryuk-era TTPs, it is almost certainly blind to their modern descendants. This post uses the sentencing as a forcing function: review the attack chain, validate your detections, and close the gaps before the next affiliate walks through the same doors.

Technical Analysis: The Ryuk Attack Chain

Initial Access and Intrusion Lifecycle

Ryuk was rarely the first payload on a host. The classic chain was:

  1. Initial access — phishing delivering loaders such as Emotet or TrickBot, or brute-forced/credentialed RDP access purchased from initial access brokers.
  2. Establishment and reconnaissance — Cobalt Strike beacons, net, nltest, and adfind enumeration, credential theft with Mimikatz-style tooling.
  3. Privilege escalation and lateral movement — PsExec against ADMIN$ over SMB (TCP 445), WMIC remote process creation, and GPO abuse to push the encryptor domain-wide.
  4. Impact — systematic anti-recovery (shadow copy and backup deletion) followed by AES-256/RSA-4096 file encryption and ransom notes (RyukReadMe.txt).

The pre-encryption dwell time — often days to weeks — is where defenders win or lose. The sentencing itself is a reminder that these intrusions are not instant: there are multiple chokepoints where a well-tuned SOC can interrupt the chain.

Key Observable Behaviors (Still Relevant to Modern Affiliates)

  • Shadow copy deletion via vssadmin delete shadows, wmic shadowcopy delete, or bcdedit recovery-disabled flags — T1490 (Inhibit System Recovery).
  • PsExec-style service installation — service binaries written to ADMIN$, service names matching PSEXESVC or randomized 8–16 character names, services.exe spawning rundll32.exe or encryptor binaries on remote hosts — T1569.002.
  • Mass file encryption — high-volume file rename/write operations appending unusual extensions, ransom notes dropped in every directory — T1486.
  • RDP exposure — externally reachable TCP 3389 as an initial access vector, often with brute-force source IPs.

Exploitation Status

Ryuk as a brand went quiet around 2020–2021 (its operators largely pivoted to Conti, then dispersed into successor groups). However, the TTPs are not historical — CISA's #StopRansomware guidance, joint advisories on LockBit, Akira, and Black Basta all describe the identical impact-phase behaviors. Treat the detections below as controls against a living threat class, not an extinct one.

Detection & Response

The rules below target the highest-signal, lowest-noise behaviors in the chain. Shadow copy deletion on servers is nearly always actionable. PsExec service installs should be rare outside your deployment tooling whitelist.

YAML
---
title: Shadow Copy Deletion via Vssadmin Wmic or Bcdedit
id: 1c8f2a4e-7b3d-4e9f-a2c1-9d5e6f7a8b9c
status: experimental
description: Detects deletion of volume shadow copies or disabling of recovery options, a hallmark ransomware anti-recovery behavior used by Ryuk and successor families.
references:
  - https://attack.mitre.org/techniques/T1490/
  - https://www.bleepingcomputer.com/news/security/ryuk-ransomware-member-sentenced-to-24-months-in-prison/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.impact
  - attack.t1490
logsource:
  category: process_creation
  product: windows
detection:
  selection_vssadmin:
    Image|endswith: '\vssadmin.exe'
    CommandLine|contains:
      - 'delete shadows'
      - 'resize shadowstorage'
  selection_wmic:
    Image|endswith: '\wmic.exe'
    CommandLine|contains: 'shadowcopy delete'
  selection_bcdedit:
    Image|endswith: '\bcdedit.exe'
    CommandLine|contains:
      - 'recoveryenabled no'
      - 'ignoreallfailures'
  condition: 1 of selection_*
falsepositives:
  - Rare; some backup agents resize shadowstorage — whitelist by process lineage
level: high
---
title: PsExec Service Binary Dropped to ADMIN Share
id: 2d9a3b5f-8c4e-5f1a-b3d2-0e6f7a8b9c0d
status: experimental
description: Detects file creation of PsExec-style service binaries in the ADMIN$ share, a primary lateral movement mechanism used by Ryuk operators to push encryptors across the domain.
references:
  - https://attack.mitre.org/techniques/T1569/002/
  - https://www.bleepingcomputer.com/news/security/ryuk-ransomware-member-sentenced-to-24-months-in-prison/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.lateral_movement
  - attack.t1021.002
  - attack.t1569.002
logsource:
  category: file_event
  product: windows
detection:
  selection_path:
    TargetFilename|contains: '\ADMIN$\'
    TargetFilename|endswith: '.exe'
  filter_legit:
    TargetFilename|contains:
      - '\SCCM\'
      - '\PatchMyPC\'
      - '\ManageEngine\'
  condition: selection_path and not filter_legit
falsepositives:
  - Legitimate remote administration and deployment tools — maintain a strict whitelist of known service binary names and hashes
level: high
---
title: Ransom Note File Creation Across Multiple Directories
id: 3e0b4c6a-9d5f-6a2b-c4e3-1f7a8b9c0d1e
status: experimental
description: Detects creation of known ransomware note filenames associated with Ryuk-style encryption campaigns.
references:
  - https://attack.mitre.org/techniques/T1486/
  - https://www.bleepingcomputer.com/news/security/ryuk-ransomware-member-sentenced-to-24-months-in-prison/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.impact
  - attack.t1486
logsource:
  category: file_event
  product: windows
detection:
  selection:
    TargetFilename|endswith:
      - '\RyukReadMe.txt'
      - '\RyukReadMe.html'
      - '\UNIQUE_ID_DO_NOT_REMOVE.txt'
falsepositives:
  - Unlikely outside of adversary emulation or IR tooling
level: critical
KQL — Microsoft Sentinel / Defender
// Hunt: Shadow copy deletion + PsExec lateral movement + ransom note artifacts
// Sentinel/Defender XDR — 7-day lookback
let lookback = 7d;
union isfuzzy=true
(DeviceProcessEvents
 | where TimeGenerated >= ago(lookback)
 | where (FileName =~ "vssadmin.exe" and ProcessCommandLine has_any ("delete shadows", "resize shadowstorage"))
      or (FileName =~ "wmic.exe" and ProcessCommandLine has "shadowcopy delete")
      or (FileName =~ "bcdedit.exe" and ProcessCommandLine has_any ("recoveryenabled no", "ignoreallfailures"))
 | project TimeGenerated, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName, Indicator = "ShadowCopyDeletion"),
(DeviceEvents
 | where TimeGenerated >= ago(lookback)
 | where ActionType == "ServiceInstalled"
 | where AdditionalFields has "PSEXESVC" or (AdditionalFields has "ADMIN$" and AdditionalFields has ".exe")
 | project TimeGenerated, DeviceName, InitiatingProcessAccountName, FileName, Indicator = "PsExecStyleServiceInstall"),
(DeviceFileEvents
 | where TimeGenerated >= ago(lookback)
 | where FileName has_any ("RyukReadMe.txt", "RyukReadMe.html", "ReadMe.txt")
 | where ActionType == "FileCreated"
 | summarize NoteCount = count(), Directories = make_set(FolderPath, 25) by DeviceName, FileName, bin(TimeGenerated, 1h)
 | where NoteCount > 5
 | project TimeGenerated, DeviceName, FileName, NoteCount, Indicator = "MassRansomNoteCreation")
| sort by TimeGenerated desc
VQL — Velociraptor
-- Hunt: Anti-recovery process execution and suspicious service binaries
SELECT Pid, Ppid, Name, CommandLine, Exe, Username, CreateTime
FROM pslist()
WHERE CommandLine =~ '(?i)(delete shadows|shadowcopy delete|recoveryenabled no|ignoreallfailures)'
   OR Exe =~ '(?i)\\\\Windows\\\\PSEXESVC'
   OR Name =~ '(?i)^(PSEXESVC|[A-Za-z0-9]{8,16})\.exe$'

The following PowerShell validates anti-recovery posture and PsExec exposure on a server fleet. Run it as part of a ransomware-readiness sweep — it makes no destructive changes; it reports state.

PowerShell
# Ryuk-style ransomware readiness audit — run as Administrator
# 1. Verify Volume Shadow Copies exist and are enabled
Write-Host "=== Shadow Copy Status ===" -ForegroundColor Cyan
Get-CimInstance Win32_ShadowCopy | Select-Object VolumeName, InstallDate | Format-Table -AutoSize
vssadmin list shadows 2>$null | Select-String -Pattern "Shadow Copy Volume"

# 2. Check recoveryenabled flag (should NOT be 'No' on production systems)
Write-Host "`n=== Boot Recovery Config ===" -ForegroundColor Cyan
bcdedit /enum {current} | Select-String -Pattern "recoveryenabled"

# 3. Audit for PsExec-style services
Write-Host "`n=== Suspicious Services ===" -ForegroundColor Cyan
Get-CimInstance Win32_Service | Where-Object {
    $_.Name -match '^PSEXESVC' -or
    ($_.PathName -match 'ADMIN\$' -and $_.PathName -match '\.exe')
} | Select-Object Name, State, PathName, StartName | Format-List

# 4. Confirm RDP is not exposed and NLA is enforced
Write-Host "`n=== RDP Hardening ===" -ForegroundColor Cyan
$rdp = Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server' -Name fDenyTSConnections
$nla = Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name UserAuthentication
Write-Host ("RDP Enabled: {0} | NLA Required: {1}" -f ($rdp.fDenyTSConnections -eq 0), ($nla.UserAuthentication -eq 1))

# 5. Verify SMB signing and SMBv1 disabled (legacy wormable paths)
Write-Host "`n=== SMB Hardening ===" -ForegroundColor Cyan
Get-SmbServerConfiguration | Select-Object EnableSMB1Protocol, RequireSecuritySignature | Format-Table -AutoSize

Write-Host "`nReview complete. Any shadow copy gaps, PsExec services, or NLA=0 findings require immediate follow-up." -ForegroundColor Yellow

Remediation and Hardening

Because this is a TTP-driven threat rather than a single patchable CVE, remediation is architectural. Prioritize:

  1. Protect backups from the blast radius. Maintain immutable or offline backups (WORM storage, object lock, or air-gapped copies). Test restoration quarterly — Ryuk operators deliberately hunted Veeam and Windows Backup infrastructure before encrypting. If your backup agent runs under domain credentials, assume it will be destroyed first.
  2. Kill the anti-recovery path. Deploy the Sigma rules above and alert — don't just log — on shadow copy deletion from servers. Constrain vssadmin, wmic, and bcdedit via WDAC/AppLocker for non-administrative contexts.
  3. Close the initial access doors. Eliminate internet-exposed RDP entirely (place it behind VPN/ZTNA with MFA and NLA). Enforce phishing-resistant MFA on all remote access and privileged accounts. Ryuk affiliates lived off stolen RDP credentials; so do their successors.
  4. Constrain lateral movement. Restrict PsExec-class tooling to a named set of deployment servers; alert on any ADMIN$ service binary creation elsewhere. Enforce SMB signing, disable SMBv1, and tier your admin model so a single compromised workstation cannot yield domain dominance.
  5. Shrink dwell time. The conviction in this case rests on intrusions that unfolded over days. Deploy EDR with behavioral (not just signature) coverage, monitor for Cobalt Strike-style beaconing and enumeration tooling, and rehearse your ransomware IR playbook — including the decision tree for isolation versus shutdown.
  6. Rehearse the worst case. Tabletop a domain-wide encryption scenario with executive leadership, legal, and communications. Review CISA's #StopRansomware guidance (cisa.gov/stopransomware) for the current joint advisory set covering successor families using identical TTPs.

Conclusion

A two-year sentence for one Ryuk operator is a modest law enforcement outcome — but for defenders, the real takeaway is operational. The crew is dispersed; the playbook is immortal. Every behavior that made Ryuk devastating — shadow copy deletion, PsExec propagation, backup destruction, domain-wide encryption — is detectable with commodity telemetry if your SOC is tuned for it. Validate the detections above in your environment this week. The next affiliate using them won't send a courtesy notice first.

Related Resources

Security Arsenal Incident Response Services AlertMonitor Platform Book a SOC Assessment incident-response Intel Hub

Is your security operations ready?

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