Sasser

Category: worm · Aliases: W32.Sasser, Worm.Win32.Sasser, Win32/Sasser.A, Sasser Worm, W32/Sasser.worm · Sample count (EMBER 2018): 25 · Enrichment: curated_sourced · Updated: 2026-10-16
Category: WormStatus: Automated SignaturePlatform: WINDOWS, WINDOWS_PEStage: Initial Access, Execution, Persistence, Lateral Movement, Impact🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 10, Windows 7, Windows XP
Executive Summary
Sasser (classified across antivirus vendors as W32.Sasser, Worm.Win32.Sasser, and Win32/Sasser) is one of the most disruptive self-replicating computer worms in the history of the internet, authored by 17-year-old German high school student Sven Jaschan (who also created the Netsky mass-mailing worm) and unleashed on April 30, 2004.

Table of Contents

Overview

Sasser (classified across antivirus vendors as W32.Sasser, Worm.Win32.Sasser, and Win32/Sasser) is one of the most disruptive self-replicating computer worms in the history of the internet, authored by 17-year-old German high school student Sven Jaschan (who also created the Netsky mass-mailing worm) and unleashed on April 30, 2004. Unlike conventional email worms of the era that required users to open an infected attachment, Sasser was completely autonomous: it scanned random IP addresses on TCP port 445 looking for unpatched systems running Microsoft Windows 2000, Windows XP, and Windows Server 2003. When an open system was identified, Sasser exploited a critical stack buffer overflow in the Local Security Authority Subsystem Service (LSASS) via the DsRolerUpgradeDownlevelServer RPC API (CVE-2004-0280 / MS04-011). The exploit triggered arbitrary shellcode execution, opening a remote command shell on TCP port 9996 and downloading the full worm executable ('avserve.exe' or 'avserve2.exe') from the attacking host via an FTP server spawned on TCP port 5554. Sasser caused lsass.exe to terminate with an unhandled exception (status code 0xC0000005), which forced Windows to display a critical system dialog with a 60-second countdown timer before automatically restarting the computer. The worm spread with such exponential ferocity that within 48 hours it infected millions of computers globally, grounding Delta Air Lines flights, closing one-third of post offices in Taiwan, halting satellite communications for French news agency AFP, and paralyzing operations at British investment banks and public hospitals. Jaschan was arrested in May 2004 following a joint investigation by German police and Microsoft.

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: Netsky

Known Derivatives & Downstream Variants: Sasser_A · Sasser_B · Sasser_C · Sasser_D

MITRE ATT&CK Techniques

This family has been observed using the following ATT&CK techniques: T1210 · T1059 · T1547.001 · T1083 · T1498

→ 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-SEAScript Execution AnalysisDetectT1059Analyze script block syntax and command arguments at runtime to detect malicious automation.
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-TRTraffic Rate LimitingIsolateT1498Deploy BGP Flowspec and edge scrubbing proxies to automatically throttle volumetric SYN and UDP reflection attacks.
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_SASSER_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Sasser"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "sasser" ascii wide nocase
        $s2 = "w32.sasser" ascii wide nocase
        $s3 = "worm.win32.sasser" ascii wide nocase
        $s4 = "win32/sasser.a" ascii wide nocase
        $s5 = "sasser worm" ascii wide nocase
        $s6 = "w32/sasser.worm" 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 - Sasser (Worm) Execution & Triage
id: dac26e01-a85f-550d-8e51-9e67f9b20fbe
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Sasser 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/sasser
- 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.t1210
- attack.t1059
- attack.t1547_001
- attack.t1083
- attack.t1498
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_SASSER_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Sasser 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 = "sasser" 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

Frequently Asked Questions

What was the Sasser worm and how did it infect computers?

Sasser was an autonomous network worm that spread in April 2004 by scanning random IP addresses and exploiting a buffer overflow in the Windows LSASS service (CVE-2004-0280 / MS04-011) over TCP port 445 without user interaction.

Why did Sasser cause computers to restart with a 60-second timer?

The exploit caused lsass.exe to crash. Because LSASS is a critical system service, Windows initiated an emergency system shutdown countdown via shutdown.exe.

Who created Sasser and what happened to the author?

Sasser was created by 17-year-old Sven Jaschan in Germany. He was arrested in May 2004 following a $250,000 bounty offered by Microsoft, and received a suspended juvenile sentence.

What major global disruptions did Sasser cause?

Sasser grounded Delta Air Lines flights, disrupted satellite communication for news agencies, forced bank branches and post offices to close, and infected hospitals across Europe and Asia.

How was Sasser mitigated?

By applying Microsoft Security Bulletin MS04-011, blocking inbound TCP port 445 at perimeter firewalls, and using removal tools to delete avserve.exe.

How do I remove the Sasser Worm from Windows?

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

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

What are the main symptoms of a Sasser infection?

Symptoms of Sasser 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 Sasser 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 threat intelligence team.

Machine-readable

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