Blaster

Category: worm · Aliases: MSBlast, Lovsan, Poosan, W32.Blaster.Worm, Win32/Blaster · Sample count (EMBER 2018): 30 · 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
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.

Table of Contents

Overview

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.

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:

Known Derivatives & Downstream Variants: Blaster_A · Blaster_B · Welchia_Nachi_Counterworm

MITRE ATT&CK Techniques

This family has been observed using the following ATT&CK techniques: T1210 · T1059 · T1547.001 · 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-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_BLASTER_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Blaster"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "blaster" ascii wide nocase
        $s2 = "msblast" ascii wide nocase
        $s3 = "lovsan" ascii wide nocase
        $s4 = "poosan" ascii wide nocase
        $s5 = "w32.blaster.worm" ascii wide nocase
        $s6 = "win32/blaster" 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 - Blaster (Worm) Execution & Triage
id: 1ce5084e-801d-5307-a86f-5e138dbccfb7
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Blaster 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/blaster
- 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.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_BLASTER_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Blaster 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 = "blaster" 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 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!!'.

How was Blaster removed and prevented?

By applying Microsoft Security Bulletin MS03-026, blocking inbound TCP port 135 and UDP port 69 at perimeter firewalls, and deleting the msblast.exe binary from System32.

How do I remove the Blaster Worm from Windows?

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

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

What are the main symptoms of a Blaster infection?

Symptoms of Blaster 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 Blaster 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/blaster.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.