Home » Worm » Sasser Worm

Sasser Worm Technical Intelligence Dossier

Category: Worm EMBER Samples: 25 Status: Curated Threat Profile
Canonical Source & Detection Telemetry

This technical brief is synchronized with the peer-reviewed threat intelligence dossier published at the SystemHelpDesk Sasser Worm Threat Profile. Review complete multi-tier YARA rules, Sigma detection rules, and REST API telemetry endpoints on the canonical authority hub.

View Canonical Dossier ↗

Executive Summary & Threat Architecture

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.

Observed Threat Aliases: W32.Sasser, Worm.Win32.Sasser, Win32/Sasser.A, Sasser Worm, W32/Sasser.worm

Ancestry & Lineage Tracking

Derived From / Upstream Ancestry: netsky

Documented Downstream Variants: sasser_a, sasser_b, sasser_c, sasser_d

Weaponized Vulnerabilities & Exploitation Topology

Documented common vulnerabilities and exposures (CVEs) weaponized by Sasser Worm operators for initial execution, sandbox evasion, or SYSTEM-level kernel privilege escalation:

CVE IdentifierExploitation ScopeOfficial Reference
CVE-2004-0280 (Canonical Catalog Hub ↗)Weaponized in in-the-wild exploitation chainsNIST NVD Advisory ↗

→ Explore all 77 exploited vulnerabilities on the SystemHelpDesk CVE Threat Matrix Hub.

MITRE ATT&CK® Tactical Tradecraft

Tactics, techniques, and procedures (TTPs) systematically mapped across real-world intrusion kill-chains:

Technique IDTechnique NameMITRE ATT&CK Framework
T1210 Exploitation Of Remote Services ATT&CK Spec ↗
T1059 Command And Scripting Interpreter ATT&CK Spec ↗
T1547.001 Boot Or Logon Autostart ATT&CK Spec ↗
T1083 File And Directory Discovery ATT&CK Spec ↗
T1498 Network Denial Of Service ATT&CK Spec ↗

→ Inspect the complete 226-technique matrix on the MITRE ATT&CK Defense Hub.

Indicators of Compromise (IOCs) & Forensic Artifacts

Curated indicators for retrospective threat hunting across SIEM and EDR platforms:

Initial Delivery Vectors

Host Persistence & Execution Hooks

Reference File Hashes (SHA-256)

Frequently Addressed 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.

Need YARA & Sigma Ingestion Files?

Export production-grade Sigma signatures, YARA detection rules, and automated SIEM ingestion feeds directly from the Official Sasser Worm Technical Portal.

Export Rules & Hashes ↗