Ryuk

Category: ransomware · Aliases: Ryuk Ransomware, Trojan.Ransom.Ryuk, Win32/Ryuk, Ransom.Ryuk, Hermes-Ryuk · Sample count (EMBER 2018): 210 · Enrichment: curated_sourced · Updated: 2026-10-16
Category: RansomwareStatus: Automated SignaturePlatform: WINDOWS, WINDOWS_PEStage: Initial Access, Execution, Persistence, Privilege Escalation, Defense Evasion, Credential Access, Lateral Movement, Impact🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
Ryuk is one of the most destructive and lucrative enterprise ransomware families in cybersecurity history, first identified in August 2018 and operated by the Russian cybercriminal syndicate Wizard Spider (tracked by threat analysts as UNC1878 and TEMP.MixMaster).

Table of Contents

Overview

Ryuk is one of the most destructive and lucrative enterprise ransomware families in cybersecurity history, first identified in August 2018 and operated by the Russian cybercriminal syndicate Wizard Spider (tracked by threat analysts as UNC1878 and TEMP.MixMaster). Derived directly from the Hermes ransomware codebase originally attributed to the Lazarus Group, Ryuk pioneered the targeted 'big game hunting' methodology against high-value commercial targets, local municipalities, and healthcare networks. Rather than deploying via indiscriminate spray-and-pray spam, Ryuk was deployed as the devastating final payload of complex multi-stage intrusion campaigns initiated by TrickBot, Emotet, or BazarLoader. Once initial network access was secured, operators conducted extensive Active Directory reconnaissance using BloodHound and AdFind, escalated privileges to Domain Admin using Zerologon (CVE-2020-1472), and mapped enterprise network shares. In a devastating technical innovation, Ryuk operators weaponized Wake-on-LAN (WOL) magic packets across local subnets to wake powered-down corporate workstations and servers before triggering encryption. Ryuk executes a multi-threaded hybrid encryption routine pairing ChaCha20 symmetric stream ciphers with RSA-4096 asymmetric public keys, appending the '.RYK' extension to targeted files. Prior to encryption, the malware terminates over 40 security and backup services using net stop, kills 150+ database and system processes via taskkill, and systematically deletes Volume Shadow Copies using vssadmin.exe delete shadows /all /quiet and bcdedit.exe to prevent system restore. CISA released Alert AA20-302A warning of widespread Ryuk ransomware attacks targeting the U.S. healthcare and public health sector.

Known aliases

Threat reports may refer to this family under multiple names:

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Derived From / Upstream Ancestry: Hermes

Known Derivatives & Downstream Variants: Ryuk_V1 · Ryuk_V2 · Ryuk_Wakeonlan · Conti_Precursor

MITRE ATT&CK Techniques

This family has been observed using the following ATT&CK techniques: T1486 · T1490 · T1021.002 · T1059.001 · T1068 · T1003.001 · T1071.001 · T1547.001

→ Explore the complete 226-Technique ATT&CK Threat Matrix

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-LSALSA Protection & Credential GuardHardenT1003.001Enable Windows LSA RunAsPPL (Protected Process Light) and Credential Guard to prevent memory dumping of lsass.exe.
D3-NBANetwork Behavioral AnalysisDetectT1021.002Enforce SMB message signing, disable legacy SMBv1, and restrict administrative share access (C$, ADMIN$) to dedicated PAM bastion hosts.
D3-PSBLPowerShell Script Block LoggingDetectT1059.001Enable PowerShell event ID 4104 and Constrained Language Mode to neuter obfuscated script payloads.
D3-KPAKernel Patching & Privilege AuditingHardenT1068Enforce rapid OS kernel patch cycles and deploy Exploit Guard protections to block memory corruption and elevation exploits.
D3-WAFWeb Content Filtering & InspectionFilterT1071.001Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles.
D3-FAEDFile Alteration Early DetectionDetectT1486Deploy canary files and monitor mass rename/encryption I/O spikes to terminate ransomware threads immediately.
D3-VSSVolume Shadow & Snapshot HardeningHardenT1490Block execution of vssadmin.exe and wmic shadowcopy delete; maintain air-gapped immutable backup repositories.
D3-RPMRegistry Persistence MonitoringDetectT1547.001Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management.

Exploited Vulnerabilities (CVEs)

This malware family is documented weaponizing the following common vulnerabilities and exposures:

Indicators of Compromise

Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.

File hashes (SHA-256, sample)

Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.

Delivery vectors

Persistence mechanisms

SIEM / EDR Ingestion: Need these reference indicators for threat hunting?

Tiered Detection Rules (Cisco CAIRN Model)

Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:

Tier 1 Primitive Artifact Rule (Fast Triage)

Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.

rule MALWARE_WIN_RYUK_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Ryuk"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "ryuk" ascii wide nocase
        $s2 = "ryuk ransomware" ascii wide nocase
        $s3 = "trojan.ransom.ryuk" ascii wide nocase
        $s4 = "win32/ryuk" ascii wide nocase
        $s5 = "ransom.ryuk" ascii wide nocase
        $s6 = "hermes-ryuk" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Tier 2 Behavioral Context Rule (Process Chains & Sigma)

Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.

title: SystemHelpDesk Detection - Ryuk (Ransomware) Execution & Triage
id: 9993c81f-9249-50f5-bf7e-46e5eed6ead1
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Ryuk malware family. Detects volume shadow copy deletion, boot status tampering,
  and recovery inhibition characteristic of modern ransomware operations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/ryuk
- https://malware-families-catalog.systemhelpdesk.com/defensive/ransomware-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.ransomware
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1486
- attack.t1490
- attack.t1021_002
- attack.t1059_001
- attack.t1068
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \vssadmin.exe
    - \wmic.exe
    - \wbadmin.exe
    - \bcdedit.exe
    CommandLine|contains:
    - delete shadows
    - shadowcopy delete
    - resize shadowstorage
    - recoveryenabled no
    - ignoreallfailures
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: critical

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_RYUK_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Ryuk tradecraft"
        tier = "T3 - Attribution Fingerprint"
        confidence = "High (Confirmed Family Signature)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        // Core family identifier & heuristic payload signatures
        $attrib_str = "ryuk" ascii wide nocase
        $pe_magic = "MZ" ascii
        $net_marker = "http" ascii nocase
    condition:
        uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

References & External Analysis

North American Authority Advisory (CISA / NIST)

The Cybersecurity and Infrastructure Security Agency (CISA) has published an official US federal advisory on this family, which can be mapped to NIST Cybersecurity Framework (CSF) incident response controls: AA20-302A ↗

Frequently Asked Questions

What is Ryuk ransomware and who operates it?

Ryuk is an enterprise-targeting ransomware family operated by Russian cybercrime group Wizard Spider (UNC1878). First discovered in August 2018, it is based on the Hermes ransomware codebase and specializes in high-value big game hunting.

How did Ryuk operators achieve lateral movement across networks?

Wizard Spider utilized TrickBot and BazarLoader for initial access, harvested Active Directory credentials with Mimikatz, exploited Zerologon (CVE-2020-1472) for domain dominance, and moved laterally using PsExec, Cobalt Strike, and WMI.

How did Ryuk use Wake-on-LAN (WOL)?

Ryuk sent Wake-on-LAN broadcast magic packets to all discovered MAC addresses on local subnets to power on sleeping workstations and laptops, ensuring maximum encryption coverage across corporate environments.

What encryption algorithms does Ryuk utilize?

Ryuk generates a unique ChaCha20 symmetric key to encrypt each file, which is then encrypted using an embedded 4096-bit RSA public key, rendering file recovery mathematically impossible without the operator's private master key.

What was the healthcare attack wave detailed in CISA Alert AA20-302A?

In October 2020, CISA, the FBI, and HHS issued Joint Advisory AA20-302A warning of an imminent, coordinated wave of Ryuk ransomware attacks aimed at crippling hospitals and healthcare providers across the United States.

How can organizations defend against Ryuk infections?

Patch Zerologon (CVE-2020-1472), restrict lateral movement via SMB and PsExec, deploy immutable offline backups, and block TrickBot and BazarLoader loaders at the email gateway.

How did Ryuk operators exploit wake-on-LAN (WOL) to encrypt offline workstations?

In advanced network intrusions, Ryuk operators integrated Wake-on-LAN (WOL) packet broadcast routines into their deployment scripts. By broadcasting magic packets across internal subnets prior to launching the encryption binary, Ryuk powered on sleeping or powered-off workstations, ensuring comprehensive encryption coverage across the entire enterprise active directory fleet.

What was the operational relationship between Ryuk, TrickBot, and the Conti ransomware syndicate?

Ryuk was operated by the elite Russian cybercrime syndicate tracked as WIZARD SPIDER. The group utilized Emotet for initial corporate email compromise, followed by TrickBot (and later BazarLoader) for network reconnaissance, privilege escalation, and lateral movement. Once domain administrator rights were obtained, WIZARD SPIDER deployed Ryuk. In late 2020, WIZARD SPIDER phased out the Ryuk codebase in favor of Conti, which featured a faster, multithreaded encryption engine.

How do I remove the Ryuk Ransomware from Windows?

Manual removal of Ryuk is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.

Is Ryuk a virus or a Ransomware?

Ryuk is classified as a Ransomware. Unlike traditional viruses that infect files, modern malware like Ryuk typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.

What are the main symptoms of a Ryuk infection?

Symptoms of Ryuk can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.

Protect Your Network Against Ransomwares

Want to prevent Ryuk and similar threats from compromising your organization? Read our comprehensive defensive guide: Ransomware Containment & Incident Response.

📣 Threat Intel Correction or Update?

Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.

Need help with an active incident? Published by the SystemHelpdesk threat intelligence team.

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/ryuk.json

Ecosystem & Interactive Environments

This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.