Wannacry

Category: ransomware_worm · Aliases: WannaCry, WanaCrypt0r, WCry, WannaCrypt, WanaCrypt0r 2.0, Ransom.WannaCry · Sample count (EMBER 2018): 4,876 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: Ransomware_WormStatus: Automated SignatureFirst seen: 2017Motivation: Financial Extortion🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 7
Executive Summary
WannaCry (cataloged across security vendors and intelligence agencies as WanaCrypt0r, WCry, WannaCrypt, and Ransom.WannaCry) is an unprecedented global ransomware worm that broke out on May 12, 2017, infecting hundreds of thousands of computers across more than 150 countries within hours.

Table of Contents

Overview

WannaCry (cataloged across security vendors and intelligence agencies as WanaCrypt0r, WCry, WannaCrypt, and Ransom.WannaCry) is an unprecedented global ransomware worm that broke out on May 12, 2017, infecting hundreds of thousands of computers across more than 150 countries within hours. Attributed by the US Department of Justice and international intelligence agencies to North Korea's Lazarus Group, WannaCry weaponized the EternalBlue SMBv1 remote code execution exploit (CVE-2017-0144) and DoublePulsar backdoor toolkit—originally leaked from the Equation Group. Once executed on a single network endpoint, WannaCry self-propagated autonomously across internal subnets and the public internet by probing TCP port 445 for vulnerable SMB services. On infected machines, WannaCry encrypted user files using AES-128 and RSA-2048 encryption, appending the .WNCRY extension, dropping ransom notes (WanaDecryptor), and demanding $300 to $600 in Bitcoin. The epidemic was famously curtailed when security researcher Marcus Hutchins discovered and registered an unregistered killswitch domain hardcoded into the binary.

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: Equation Group Fuzzbunch · Eternalblue Exploitation Framework

Known Derivatives & Downstream Variants: Wannacry 1.0 · Wanacrypt0R 2.0 · Wannacry Killswitch Variant

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

→ 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-WAFWeb Content Filtering & InspectionFilterT1071.001Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles.
D3-FDAFile Directory Access AuditingDetectT1083Audit and alert on high-frequency recursive directory queries executed by non-system and unclassified binaries.
D3-NPSNetwork Protocol Segmentation & PatchingFilterT1210Disable legacy protocols (e.g. SMBv1) and restrict SMB/RPC lateral movement across internal subnet boundaries.
D3-FAEDFile Alteration Early DetectionDetectT1486Deploy canary files and monitor mass rename/encryption I/O spikes to terminate ransomware threads immediately.
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_WANNACRY_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Wannacry"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "wannacry" ascii wide nocase
        $s2 = "wannacry" ascii wide nocase
        $s3 = "wanacrypt0r" ascii wide nocase
        $s4 = "wcry" ascii wide nocase
        $s5 = "wannacrypt" ascii wide nocase
        $s6 = "wanacrypt0r 2.0" ascii wide nocase
        $s7 = "ransom.wannacry" 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 - Wannacry (Ransomware Worm) Execution & Triage
id: df66d53e-9fa8-57d3-9efe-92ed860aa08a
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Wannacry malware family. Detects suspicious execution from temporary user
  directories with hidden window flags and background transfer utilities.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/wannacry
- 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-worm
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1486
- attack.t1210
- attack.t1083
- attack.t1547_001
- attack.t1071_001
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \cmd.exe
    - \powershell.exe
    - \cscript.exe
    - \wscript.exe
    CommandLine|contains:
    - AppData\Local\Temp
    - -WindowStyle Hidden
    - /e:jscript
    - bitsadmin /transfer
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: medium

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_WANNACRY_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Wannacry 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 = "wannacry" 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)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

  1. Isolate all infected and vulnerable Windows hosts from internal and external networks immediately.
  2. Block inbound and outbound TCP port 445 (SMB) across all network firewalls and router interfaces.
  3. Terminate active WannaCry encryption processes and kill mssecsvc.exe and tasksche.exe.
  4. Deploy Microsoft security update MS17-010 to patch SMBv1 vulnerabilities across all endpoints.
  5. Ensure sinkhole DNS resolutions for the hardcoded killswitch domain are permitted out to the internet.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

  1. Do not allow SMBv1 protocol to remain enabled in modern enterprise infrastructure.
  2. Avoid leaving port 445 exposed directly to the public internet.
  3. Do not sinkhole the killswitch domain internally with NXDOMAIN responses, which would trigger live payload detonation.

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: https://www.cisa.gov/news-events/alerts/2017/05/12/multiple-ransomware-infections-reported ↗

Frequently Asked Questions

What is the WannaCry ransomware worm?

WannaCry is a global ransomware worm that exploited the EternalBlue SMBv1 flaw to infect hundreds of thousands of computers worldwide in May 2017.

Which vulnerability did WannaCry exploit to propagate?

WannaCry weaponized CVE-2017-0144 (MS17-010 / EternalBlue), allowing unauthenticated remote code execution over SMBv1 port 445.

Who was responsible for the WannaCry attack?

The United States Department of Justice and international cyber agencies formally attributed WannaCry to North Korea's state-sponsored Lazarus Group.

How was the WannaCry outbreak halted?

Security researcher Marcus Hutchins registered an unregistered sinkhole domain hardcoded into the worm's binary that functioned as an unintended killswitch.

How can systems be protected against WannaCry and similar threats?

Apply MS17-010 security updates, completely disable SMBv1 across all operating systems, and block port 445 at network perimeter firewalls.

How did the DoublePulsar backdoor interact with EternalBlue (MS17-010) during WannaCry's propagation phase?

WannaCry incorporated the NSA-attributed EternalBlue exploit (CVE-2017-0144) to exploit a buffer overflow in Microsoft's SMBv1 protocol over port 445. Once the exploit succeeded, WannaCry installed the DoublePulsar ring-0 kernel backdoor into system memory. DoublePulsar then injected the WannaCry launcher DLL directly into the lsass.exe process, executing the ransomware with full SYSTEM privileges without touching disk.

What was the technical mechanism behind Marcus Hutchins' kill-switch domain registration that halted WannaCry's global spread?

Prior to executing its encryption routine, WannaCry attempted an HTTP GET request to an unregistered, hardcoded sinkhole domain (www.iuqerfsodp9ifjaposdfjhgosurijfaewrwergwea.com). If the domain query returned a failure (as it did initially when unregistered), WannaCry proceeded with encryption and worm propagation. When cybersecurity researcher Marcus Hutchins registered the domain, subsequent queries returned an active HTTP 200 response, causing the malware's built-in sandbox-evasion logic to terminate execution automatically.

How do I remove the Wannacry Ransomware_Worm from Windows?

Manual removal of Wannacry 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 Wannacry a virus or a Ransomware_Worm?

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

What are the main symptoms of a Wannacry infection?

Symptoms of Wannacry 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 Ransomware_Worms

Want to prevent Wannacry 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/wannacry.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.

🛡️ Verified Antivirus Support & Customer Assistance

Experiencing issues with unexpected malware infections, persistent adware popups, or security software licensing? Access our verified resolution guides and official customer support helplines:

→ View all 57 TotalAV Antivirus & Security Support Resources