Netsky

Category: worm · Aliases: Netsky, Worm.Win32.Netsky, W32/Netsky, Win32.Netsky, Moodown · Sample count (EMBER 2018): 105 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: WormStatus: Automated SignaturePlatform: WINDOWS, X86Stage: Initial-Access, Execution, Persistence, Collection, Lateral-MovementFirst seen: 2004Actor: Sven JaschanIndustry: consumers, education, corporate_networks, telecommunicationsMotivation: Digital Vandalism & Malware Turf War🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 10, Windows 7, Windows XP
Executive Summary
Worm:Win32/Netsky is a historically monumental, prolific mass-mailing computer worm that emerged in February 2004, causing tens of millions of dollars in global network congestion and computer disruptions.

Table of Contents

Overview

Worm:Win32/Netsky is a historically monumental, prolific mass-mailing computer worm that emerged in February 2004, causing tens of millions of dollars in global network congestion and computer disruptions. Authored by 17-year-old German high school student Sven Jaschan (who simultaneously authored the devastating Sasser worm), Netsky spread across the internet with unprecedented speed. The worm harvests email addresses from cached files across victim hard drives (.html, .eml, .txt, .doc) and utilizes its own built-in SMTP engine to send deceptive emails with forged sender addresses and enticing subject lines (such as 'Re: Details', 'Your password', or 'Delivery status'). Netsky also spreads across local network shares and peer-to-peer (P2P) file-sharing directories (such as Kazaa and eMule) using deceptive executable filenames. Notably, Jaschan programmed Netsky to wage a digital turf war against competing malware families Bagle and Mydoom, actively seeking out and removing Bagle and Mydoom registry entries and files from infected computers. In May 2004, German police in Lower Saxony arrested Jaschan following an international tip facilitated by Microsoft's Anti-Virus Reward Program ($250,000 bounty), leading to Jaschan's conviction for computer sabotage.

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: Netsky.A · Netsky.B · Netsky.C · Netsky.D (Peak Outbreak) · Netsky.P · Netsky.Z

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-NBANetwork Behavioral AnalysisDetectT1021.002Enforce SMB message signing, disable legacy SMBv1, and restrict administrative share access (C$, ADMIN$) to dedicated PAM bastion hosts.
D3-PBAProcess Spawn AnalysisDetectT1059.003Inspect command-line arguments and anomalous parent-child relationships spawning from cmd.exe.
D3-ALPAApplication Layer Protocol AnalysisDetectT1071.003Fingerprint application traffic structures and enforce TLS inspection for external outbound sessions.
D3-EAMEmail Access MonitoringDetectT1114.001Monitor Graph API and MAPI email harvesting routines and alert on bulk email downloads originating from unusual IP addresses.
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.

ProtocolsSMTP, P2P, TCP
Observed ports25, 139, 445
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_NETSKY_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Netsky"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "netsky" ascii wide nocase
        $s2 = "netsky" ascii wide nocase
        $s3 = "worm.win32.netsky" ascii wide nocase
        $s4 = "w32/netsky" ascii wide nocase
        $s5 = "win32.netsky" ascii wide nocase
        $s6 = "moodown" 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 - Netsky (Worm) Execution & Triage
id: e3cc925b-5edd-5997-b251-534eaf8e953a
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Netsky 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/netsky
- 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.worm
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1566_002
- attack.t1114_001
- attack.t1021_002
- attack.t1071_003
- attack.t1560_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_NETSKY_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Netsky 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 = "netsky" 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 outbound direct port 25 SMTP traffic from user endpoints to stop worm propagation.
  2. Deploy email gateway filters inspecting executable attachments with double extensions (.pif, .scr, .exe).
  3. Disable open writable network shares across corporate subnets.
  4. Apply security patch MS04-011 for LSASS vulnerability CVE-2004-0115.

What to Avoid

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

  1. Do not allow direct outbound port 25 access from client subnets without relaying through trusted mail servers.
  2. Avoid opening unsolicited email attachments ending in .pif, .scr, or .cmd.
  3. Do not operate unauthenticated file-sharing services across untrusted networks.

References & External Analysis

Frequently Asked Questions

What was the Netsky worm?

Netsky was a fast-spreading mass-mailing worm that infected millions of computers worldwide in 2004 via email and peer-to-peer networks.

Who wrote the Netsky worm?

Netsky was written by 17-year-old German student Sven Jaschan, who was also responsible for creating the Sasser worm.

How was Sven Jaschan captured?

Jaschan was arrested by German police in May 2004 following an informant tip rewarded by Microsoft's $250,000 Anti-Virus Reward Program.

What was the malware 'turf war' between Netsky, Bagle, and Mydoom?

Jaschan coded Netsky to actively find and delete registry keys, processes, and files of rival worms Bagle and Mydoom, claiming to clean infected computers.

How did Netsky propagate without an email client?

Netsky contained its own internal SMTP engine, allowing it to connect directly to recipient mail servers to deliver forged emails.

How do I remove the Netsky Worm from Windows?

Manual removal of Netsky 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 Netsky a virus or a Worm?

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

What are the main symptoms of a Netsky infection?

Symptoms of Netsky 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 Worms

Want to prevent Netsky and similar threats from compromising your organization? Read our comprehensive defensive guide: Worm & Virus Protection.

📣 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/netsky.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.