Klez
Table of Contents
Overview
Worm:Win32/Klez is a historic, highly destructive mass-mailing worm that first appeared in late 2001 and raged across the internet for years. Klez fundamentally changed the landscape of malware by being one of the first major worms to utilize **'Sender Spoofing'**. By forging the 'From:' address in its emails, it caused massive confusion, resulting in innocent users being accused of spreading the virus, and making the true source of the infection incredibly difficult to track down.
Understanding the Klez Worm
To an infected user, the computer might slow down, and their antivirus software would suddenly stop working. To the rest of the world, it appeared as if everyone was emailing the virus to everyone else. For security analysts, Klez represents the peak of the mass-mailing worm era. It was highly aggressive, exploiting an unpatched vulnerability in Microsoft Outlook/Internet Explorer that allowed the malicious attachment to execute *automatically* just by viewing the email in the preview pane.
Propagation and Spoofing Mechanics
The infection cycle begins when a victim receives a seemingly legitimate email containing the Klez executable. It exploited the `IFRAME` vulnerability (CVE-2001-0154) (`T1190`) to execute without user interaction (`T1204`). Upon execution, Klez drops itself into the Windows System folder and establishes persistence (`T1547.001`). Its core function is propagation (`T1534`). It scans the victim's hard drive for email addresses (in address books, cached web pages, and documents). When sending a copy of itself, Klez randomly selects an address from the victim's address book to place in the 'To:' field, and crucially, selects *another* random address to place in the 'From:' field (Sender Spoofing). Furthermore, Klez actively attempts to disable and delete dozens of popular antivirus programs to ensure its survival (`T1562.001`).
Indicators of Compromise & Impact
The primary impact was massive network congestion, reputational damage due to spoofing, and the disabling of endpoint security. The most glaring IoC is an overwhelming surge in outbound SMTP traffic on port 25 originating from the endpoint. Host-based IoCs include EDR alerts for the sudden, forceful termination of antivirus processes and the creation of randomly named executables in the `%SystemRoot%`.
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
| Technique | Name | Tactic | Official Spec |
|---|---|---|---|
T1534 | Internal Spearphishing (Mass-mailing propagation) | Lateral Movement | ATT&CK ↗ |
T1190 | Exploit Public-Facing Application (Exploiting Outlook IFRAME vulnerability) | Initial Access | ATT&CK ↗ |
T1562.001 | Impair Defenses: Disable or Modify Tools (Killing AV processes) | Defense Evasion | ATT&CK ↗ |
T1547.001 | Boot or Logon Autostart Execution: Registry Run Keys | Persistence | ATT&CK ↗ |
MITRE D3FEND™ Defensive Countermeasures
Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-RPM | Registry Persistence Monitoring | Detect | T1547.001 | Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management. |
D3-STA | Security Tool Anti-Tamper Enforcement | Harden | T1562.001 | Block unauthorized modification of antivirus registry flags and prevent stopping security agent services. |
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_KLEZ_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Klez"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "klez" 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 - Klez (Advanced Threat) Execution & Triage
id: 55ab14b9-d60c-52b8-ad1a-677a02d52656
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Klez malware family. Detects proxy execution, reflective DLL loading, and
remote command injection associated with modular enterprise backdoors.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/klez
- https://malware-families-catalog.systemhelpdesk.com/defensive/backdoor-rat-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.advanced-threat
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1190
- attack.t1547_001
- attack.t1534
- attack.t1562_001
logsource:
category: process_creation
product: windows
detection:
selection_process:
Image|endswith:
- \powershell.exe
- \cmd.exe
- \rundll32.exe
- \regsvr32.exe
CommandLine|contains:
- DownloadString
- IEX(
- '/s /n /u /i:'
- sc create
- start-process
condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: highTier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_KLEZ_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Klez 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 = "klez" 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
}Containment & Response Steps
Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.
- Isolate the endpoint from the network immediately to halt the mass-mailing engine and stop the outbound flood of infected emails.
- Block outbound SMTP (Port 25) traffic at the enterprise firewall for all workstations, ensuring only authorized mail servers can send email.
- Ensure the endpoint's antivirus is actually running, as Klez explicitly targets and disables security software.
- Deploy the MS01-020 (or cumulative) patch for Internet Explorer to prevent the automatic execution vulnerability.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not trust the 'From:' address of a Klez-infected email; the person listed there is almost certainly innocent and likely not the source of the infection.
- Avoid assuming the threat is modern; Klez relies on early 2000s exploits, so an infection indicates severely outdated software.
References & External Analysis
- Search "klez" on VirusTotal (External Analysis)
- Search "klez" on Any.Run (Sandbox Sandbox)
- Search "klez" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Klez and what threat category does it belong to?
Klez is classified as a Advanced Threat. Documented across security telemetry, it is engineered to execute unauthorized operations, establish persistent footholds on target endpoints, and facilitate malicious campaigns targeting enterprise and individual environments.
How does Klez establish persistence and evade defensive controls?
Klez typically establishes persistence through registry run keys, scheduled tasks, or service installations, while evading signature-based antivirus solutions through code obfuscation, memory injection, or anti-analysis sandbox checks.
What are the essential incident response steps for mitigating a Klez compromise?
Security teams responding to Klez should immediately isolate affected endpoints from the network, perform memory triage to capture volatile forensic artifacts, audit registry and startup persistence mechanisms, revoke exposed user credentials, and restore systems from verified, clean backups.
What lateral movement and credential access tactics does Klez leverage in enterprise intrusions?
Klez frequently utilizes privileged account harvesting techniques such as LSASS memory dumping, Kerberoasting, and token impersonation to escalate privileges. Once administrative credentials are acquired, it pivots across the victim network utilizing living-off-the-land binaries (LOLBins) such as WMI, PowerShell remoting, and PsExec, or abuses remote desktop protocols (RDP) to reach critical internal repositories and domain controllers.
How does Klez maintain covert communications and evade perimeter network monitoring?
Klez often relies on multi-stage command and control (C2) architectures utilizing encrypted protocols over standard web ports (HTTPS/443 or DNS tunneling) to blend in with legitimate enterprise network traffic. Many variants incorporate proxy networks, domain fronting, or cloud services (such as Microsoft Graph API, Google Drive, or Telegram) to masquerade C2 channels, bypassing traditional signature-based egress filtering.
How do I remove the Klez Advanced_Threat from Windows?
Manual removal of Klez 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 Klez a virus or a Advanced_Threat?
Klez is classified as a Advanced_Threat. Unlike traditional viruses that infect files, modern malware like Klez typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Klez infection?
Symptoms of Klez 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 Advanced_Threats
Want to prevent Klez and similar threats from compromising your organization? Read our comprehensive defensive guide: Think You've Been Hacked? What To Do First.
📣 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.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/klez.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.