Zombieboy
Table of Contents
Overview
Trojan:Win32/Zombieboy is a highly aggressive, self-propagating cryptomining botnet (Worm) that emerged prominently around 2018. It is infamous for rapidly spreading across enterprise networks by aggressively weaponizing a suite of leaked NSA exploits—most notably EternalBlue (`T1210`) and DoublePulsar. Its primary objective is not data theft or ransomware, but rather to forcibly co-opt the CPU resources of infected machines to mine Monero (XMR) cryptocurrency (`T1496`).
Understanding Zombieboy (Cryptomining Worms)
To an end-user, a Zombieboy infection manifests as severe, unexplained system sluggishness and high CPU temperatures. For a security operations center (SOC), Zombieboy is a 'noisy' but critical threat. While cryptomining is less destructive than ransomware, the fact that Zombieboy successfully exploited a machine indicates a severe vulnerability management failure; the same vector could easily be used to deploy ransomware.
Execution and Propagation Mechanics
Zombieboy is primarily a network worm. Once a single machine on a network is infected (often via phishing or an exposed vulnerability), the bot immediately begins scanning the internal subnet (`T1046`) for port 445 (SMB). When it finds an unpatched machine, it fires the EternalBlue exploit (`T1210`) to gain SYSTEM-level access, subsequently using the DoublePulsar backdoor to install itself. It establishes persistence via WMI event subscriptions (`T1546.003`) or scheduled tasks. It then drops an open-source XMRig miner (often renamed), configures it to point to a mining pool, and begins monopolizing the CPU (`T1496`). To maintain dominance, it often attempts to kill competing cryptominers on the host.
Indicators of Compromise & Impact
The primary impact is massive resource exhaustion and the realization of unpatched critical vulnerabilities. Host-based IoCs include the presence of `XMRig.exe` or heavily obfuscated binaries consuming 90%+ CPU in Task Manager, and the creation of anomalous WMI Event Consumers. Network IoCs are highly prominent: massive spikes in internal port 445 (SMB) scanning traffic originating from standard workstations, and outbound connections to known Stratum mining pool IP addresses over ports like 3333, 4444, or 8080.
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
MITRE D3FEND™ Defensive Countermeasures
Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-PSA | Port Scan Analysis | Detect | T1046 | Deploy network intrusion detection (NIDS) to identify sequential TCP SYN scans and unauthorized subnet reconnaissance. |
D3-NPS | Network Protocol Segmentation & Patching | Filter | T1210 | Disable legacy protocols (e.g. SMBv1) and restrict SMB/RPC lateral movement across internal subnet boundaries. |
D3-PEA | Processor Execution Auditing | Detect | T1496 | Alert on sustained high CPU/GPU utilization by processes originating from temporary user directories and block stratum mining pool ports. |
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_ZOMBIEBOY_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Zombieboy"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "zombieboy" 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 - Zombieboy (Ransomware) Execution & Triage
id: 2b8e56cd-2cd6-58a2-99f4-0a4196699f7a
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Zombieboy 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/zombieboy
- 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.t1210
- attack.t1496
- attack.t1046
- attack.t1546_003
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: criticalTier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_ZOMBIEBOY_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Zombieboy 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 = "zombieboy" 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
}Containment & Response Steps
Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.
- Immediately apply Microsoft security patch MS17-010 (addressing the EternalBlue SMBv1 vulnerability) to ALL systems on the network.
- Isolate infected machines to stop the internal scanning and propagation.
- Block outbound connections to known cryptomining pools at the perimeter firewall (often using the Stratum protocol).
- Hunt for and remove the WMI event subscriptions and dropped XMRig binaries used by the malware for persistence.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not treat cryptomining as a 'low priority' alert; a worm moving via EternalBlue means your network is fully exposed to more severe threats.
- Avoid simply killing the high-CPU process; the WMI persistence mechanism will restart it immediately.
References & External Analysis
- Search "zombieboy" on VirusTotal (External Analysis)
- Search "zombieboy" on Any.Run (Sandbox Sandbox)
- Search "zombieboy" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Zombieboy and what threat category does it belong to?
Zombieboy is classified as a Ransomware. Documented across security telemetry, it is engineered to execute unauthorized operations, establish persistent footholds on target endpoints, and facilitate malicious campaigns targeting enterprise and individual environments.
How does Zombieboy establish persistence and evade defensive controls?
Zombieboy typically establishes persistence through registry run keys, scheduled tasks, or service installations, while evading signature-based antivirus solutions through code obfuscation, memory injection, or anti-analysis sandbox checks.
What are the essential incident response steps for mitigating a Zombieboy compromise?
Security teams responding to Zombieboy should immediately isolate affected endpoints from the network, perform memory triage to capture volatile forensic artifacts, audit registry and startup persistence mechanisms, revoke exposed user credentials, and restore systems from verified, clean backups.
What cryptographic algorithms and file targeting techniques does Zombieboy employ during execution?
Zombieboy typically leverages hybrid cryptographic architectures combining symmetric stream or block ciphers (such as AES-256 or ChaCha20) for rapid file encryption with asymmetric algorithms (such as RSA-2048 or Curve25519) to securely protect the session keys. It aggressively targets sensitive file extensions including corporate documents, databases, virtual disks, and backups while systematically executing commands to delete Volume Shadow Copies (vssadmin delete shadows /all /quiet) and disable system recovery options.
Are decryptors available for Zombieboy, and what is the recommended recovery procedure?
Decryption availability for Zombieboy depends on whether security researchers or law enforcement (such as the No More Ransom initiative) have recovered the master private keys or discovered flaws in its key generation routines. Victims should never pay the extortion demand, as payment fuels criminal operations without guaranteeing file restoration. The recommended recovery procedure entails isolating infected hosts, conducting forensic disk imaging, identifying the root access vector, and restoring validated systems from immutable offline backups.
How do I remove the Zombieboy Ransomware from Windows?
Manual removal of Zombieboy 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 Zombieboy a virus or a Ransomware?
Zombieboy is classified as a Ransomware. Unlike traditional viruses that infect files, modern malware like Zombieboy typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Zombieboy infection?
Symptoms of Zombieboy 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 Zombieboy 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.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/zombieboy.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.