Home » Worm » Blaster (Lovsan) Worm

Blaster (Lovsan) Worm Technical Intelligence Dossier

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

This technical brief is synchronized with the peer-reviewed threat intelligence dossier published at the SystemHelpDesk Blaster (Lovsan) 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

Blaster (also widely cataloged as MSBlast, Lovsan, and Poosan) is one of the most famous and destructive self-propagating computer worms in internet history, first detected on August 11, 2003. Propagating at machine speed across the global IPv4 address space without requiring any email opening, attachment execution, or user interaction, Blaster scanned random IP subnets on TCP port 135 to find unpatched endpoints running Microsoft Windows 2000 and Windows XP. When an open port was found, Blaster exploited a critical stack buffer overflow in the Distributed Component Object Model (DCOM) interface of the Windows RPCSS service (CVE-2003-0352 / MS03-026). Once code execution was achieved, Blaster spawned an unauthenticated remote command shell on TCP port 4444 and instructed the compromised endpoint to download the full worm binary ('msblast.exe') from the attacking host via Trivial File Transfer Protocol (TFTP) over UDP port 69. The worm payload contained hidden text strings taunting Microsoft's founder ('billy gates why do you make this possible ? Stop making money and fix your software!!'). Additionally, Blaster was programmed to launch a coordinated distributed denial-of-service (DDoS) SYN flood against port 80 of windowsupdate.com starting on August 15, 2003, forcing Microsoft to temporarily take the Windows Update portal offline to protect global internet routing infrastructure. Blaster infected hundreds of thousands of computers worldwide within days, severely degrading internet traffic and accelerating the creation of modern Windows security baselines.

Observed Threat Aliases: MSBlast, Lovsan, Poosan, W32.Blaster.Worm, Win32/Blaster

Ancestry & Lineage Tracking

Derived From / Upstream Ancestry: Proprietary origin

Documented Downstream Variants: blaster_a, blaster_b, welchia_nachi_counterworm

Weaponized Vulnerabilities & Exploitation Topology

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

CVE IdentifierExploitation ScopeOfficial Reference
CVE-2003-0352 (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 ↗
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 Blaster (MSBlast) worm and how did it spread?

Blaster was an autonomous network worm that exploded in August 2003 by exploiting a DCOM RPC buffer overflow (CVE-2003-0352 / MS03-026) on TCP port 135 across Windows 2000 and XP systems.

What payload did Blaster drop on infected systems?

Blaster opened a remote shell on TCP port 4444 and downloaded msblast.exe into the Windows System32 directory using TFTP on UDP port 69.

What was Blaster's planned DDoS attack?

It contained code to launch a coordinated SYN flood against windowsupdate.com starting August 15, 2003, forcing Microsoft to redirect update traffic to prevent internet outages.

What message was hidden in the Blaster binary?

It contained the strings 'I just want to say LOVE YOU SAN!!' and 'billy gates why do you make this possible ? Stop making money and fix your software!!'.

Need YARA & Sigma Ingestion Files?

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

Export Rules & Hashes ↗