Storm

Category: botnet · Aliases: Storm, Storm Worm, Peed, Nuwar, W32/Storm, Dorf · Sample count (EMBER 2018): 1 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: BotnetStatus: Automated SignaturePlatform: WINDOWS, X86Stage: Initial-Access, Execution, Persistence, Command-And-Control, ImpactFirst seen: 2007Actor: Storm SyndicateIndustry: consumers, financial_services, isp_providers, telecommunicationsMotivation: Spam Syndication, Stock Manipulation & DDoS Retaliation🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 7
Executive Summary
Worm:Win32/Storm (universally documented in cybersecurity literature as the Storm Worm, Peed, and Nuwar) was a revolutionary peer-to-peer (P2P) botnet that infected an estimated 10 million computers worldwide between 2007 and 2008.

Table of Contents

Overview

Worm:Win32/Storm (universally documented in cybersecurity literature as the Storm Worm, Peed, and Nuwar) was a revolutionary peer-to-peer (P2P) botnet that infected an estimated 10 million computers worldwide between 2007 and 2008. Storm revolutionized malware architecture by pioneering two foundational cybercrime innovations: the use of the decentralized Overnet/Kademlia P2P communication protocol (eliminating centralized C2 servers) and Fast-Flux DNS service networks. Storm lured victims through sensationalized social engineering email spam capitalizing on European storm disasters (such as '230 dead as storm batters Europe'), celebrity scandals, and holiday greeting cards. The botnet was weaponized for high-volume email spam, financial stock manipulation, and defensive DDoS retaliation attacks against security researchers, CERTs, and spam-tracking organizations (including Spamhaus) that attempted to investigate its infrastructure. Storm served as the direct technological progenitor to subsequent P2P botnets including Waledac and Kelihos before being systematically countered by vendor endpoint removals and Overnet protocol poisoning.

Known aliases

Threat reports may refer to this family under multiple names:

Threat Actor Attribution

Attribution is probabilistic, not a science. Each link below states its confidence level and the evidence behind it.

→ Explore all Threat Actor & APT Campaign Profiles

Family Pedigree & Lineage

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

Known Derivatives & Downstream Variants: Storm Worm Original (2007) · Storm Fast-Flux Edition · Waledac (Successor) · Kelihos (Successor)

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-PBAProcess Spawn AnalysisDetectT1059.003Inspect command-line arguments and anomalous parent-child relationships spawning from cmd.exe.
D3-WAFWeb Content Filtering & InspectionFilterT1071.001Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles.
D3-TRTraffic Rate LimitingIsolateT1498Deploy BGP Flowspec and edge scrubbing proxies to automatically throttle volumetric SYN and UDP reflection attacks.
D3-URLRURL Rewriting & Time-of-Click InspectionFilterT1566.002Rewrite all external email links to force real-time URL reputation and DNS resolution at click time.

Exploited Vulnerabilities (CVEs)

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

Command & Control (C2) and Network Profile

How this family talks to its operators. C2 traffic can often identify a family even when its code and configuration are hard to analyse. Ports and patterns are historical and change between campaigns, so use them as hunting leads rather than block-only rules.

ProtocolsP2P, HTTP, DNS
Observed ports80, 407, 53
Identifiable from traffic aloneHigh

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_STORM_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Storm"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "storm" ascii wide nocase
        $s2 = "storm" ascii wide nocase
        $s3 = "storm worm" ascii wide nocase
        $s4 = "peed" ascii wide nocase
        $s5 = "nuwar" ascii wide nocase
        $s6 = "w32/storm" ascii wide nocase
        $s7 = "dorf" 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 - Storm (Botnet) Execution & Triage
id: 81d2793a-dae0-5916-ad41-7f414b484f51
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Storm malware family. Detects firewall rule subversion, internal port proxying,
  and command-and-control keepalive polling indicative of botnet nodes.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/storm
- https://malware-families-catalog.systemhelpdesk.com/defensive/botnet-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.botnet
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1566_002
- attack.t1568_001
- attack.t1071_001
- attack.t1498
- attack.t1059_003
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \netsh.exe
    - \route.exe
    - \arp.exe
    - \ping.exe
    CommandLine|contains:
    - advfirewall firewall add rule
    - netsh interface portproxy
    - ping -n 1 127.0.0.1
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_STORM_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Storm 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 = "storm" 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. Block Overnet / eDonkey P2P protocol traffic on perimeter firewalls.
  2. Deploy DNS response inspection rules detecting short-TTL fast-flux domain patterns.
  3. Filter inbound email for social engineering headlines referencing current breaking news and natural disasters.
  4. Apply security patch MS07-017 addressing Windows Animated Cursor vulnerability CVE-2007-0038.

What to Avoid

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

  1. Do not click executable download links in breaking-news email alerts from unverified news domains.
  2. Avoid allowing unrestricted outbound P2P networking protocols from corporate workstations.
  3. Never probe live botnet C2 nodes from non-isolated analysis networks.

References & External Analysis

Frequently Asked Questions

What was the Storm Worm botnet?

Storm Worm was a massive peer-to-peer botnet that infected an estimated 10 million computers in 2007 using social engineering emails and Fast-Flux DNS.

What architectural innovations did Storm Worm introduce?

Storm was the first major malware to use decentralized Overnet P2P protocols for C2 and Fast-Flux DNS to rapidly cycle IP addresses for bulletproof availability.

How did Storm Worm retaliate against security researchers?

Storm automatically initiated retaliatory DDoS attacks against IP addresses and research organizations that probed or monitored its P2P nodes.

What subsequent malware was derived from Storm Worm?

Storm Worm's P2P codebase served as the direct foundational predecessor for Waledac and the Kelihos/Hlux botnets.

What vulnerabilities were exploited by Storm Worm?

Storm exploited browser and media vulnerabilities including CVE-2006-4704 and CVE-2007-0038 via drive-by download staging sites.

How do I remove the Storm Botnet from Windows?

Manual removal of Storm 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 Storm a virus or a Botnet?

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

What are the main symptoms of a Storm infection?

Symptoms of Storm 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 Botnets

Want to prevent Storm and similar threats from compromising your organization? Read our comprehensive defensive guide: Botnet Protection & Remediation.

📣 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 team.

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/storm.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.