Lethic

Overview

Lethic is a notorious, long-running spam-distribution botnet that first emerged in 2008. Designed specifically as an automated email transmission engine for Eastern European cybercrime operations, Lethic compromised hundreds of thousands of Windows PCs worldwide to blast billions of unauthorized emails peddling illicit pharmaceuticals, counterfeit designer goods, financial scams, and malware dropper attachments. In January 2010, international cybersecurity researchers and upstream Tier-1 internet service providers executed a coordinated takedown, disconnecting Lethic's primary command and control infrastructure in the Netherlands and Ukraine, which caused global spam volumes to temporarily drop by more than 10%. However, the operators demonstrated remarkable operational agility, rapidly reactivating the botnet within weeks by utilizing hardcoded backup IP ranges and encrypted fallback communication channels. Lethic employs a lightweight client implant that receives encrypted email templates and recipient lists over custom TCP ports, directly dispatching high-volume SMTP connections on port 25 without alerting the workstation user.

Known aliases

Threat reports may refer to this family under multiple names:

• Lethic
• SpamBot.Lethic
• Trojan.Lethic
• Win32/Lethic

Threat Actor Attribution

Attribution is probabilistic, not a science. Each link below states its confidence level and the evidence behind it.

• Eastern European Cybercrime Spammers (Lethic Syndicate) High confidence
  Basis: Active since 2008 as a massive specialized spam-generating botnet. Subject to a coordinated multinational ISP and research takedown in January 2010 that disabled primary C2 infrastructure. The operators rebuilt the network with redundant backup nodes and encrypted binary protocols. [source]

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: Lethic V1 · Lethic V2 · Lethic-Proxy

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

• T1059.003: Restrict execution of Windows Command Shell (cmd.exe) and block unauthorized batch scripts.
• T1071.001: Implement web filtering and SSL/TLS inspection to detect malicious command and control (C2) traffic hiding in HTTP/HTTPS.

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

Exploited Vulnerabilities (CVEs)

This malware family is documented weaponizing the following common vulnerabilities and exposures:

• CVE-2010-0805 — In-depth exploitation analysis and catalog intelligence (NIST NVD ↗).

Command & Control (C2) and Network Profile

How this family talks to its operators. C2 traffic can often identify a family even when its code and configuration are hard to analyse. Ports and patterns are historical and change between campaigns, so use them as hunting leads rather than block-only rules.

Network detection ideas

• Detect high volumes of outbound SMTP (TCP port 25) connections initiated from desktop endpoints rather than approved enterprise mail transfer agents (MTAs)
• Alert on long-lived TCP sessions on non-standard ports transmitting encrypted spam template commands
• Block C2 IP addresses associated with Lethic botnet control nodes

Sources: CISA Advisory AA20-302A, Malpedia Lethic

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.

• 0f6222bfa8952467d027e8529348d6132646d5ee3269b2d887349176ca0cf508
• 59b48c4cf667b9370cecb393d987d6eec08fdf569da89178bf7493a38ce3722b

Delivery vectors

• Drive-by downloads from compromised websites
• Secondary downloads by trojan loaders and worms

Persistence mechanisms

• Registry Run key in HKLM\Software\Microsoft\Windows\CurrentVersion\Run
• Service installation disguised as a Windows networking or background diagnostic utility

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:

rule MALWARE_WIN_LETHIC_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Lethic"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "lethic" ascii wide nocase
        $s2 = "lethic" ascii wide nocase
        $s3 = "spambot.lethic" ascii wide nocase
        $s4 = "trojan.lethic" ascii wide nocase
        $s5 = "win32/lethic" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Lethic (Spam Bot) Execution & Triage
id: 4c8711a2-2ee6-5204-b7a0-cad2d94d7830
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Lethic 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/lethic
- 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.spam-bot
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1071_001
- attack.t1498
- attack.t1547_001
- attack.t1059_003
- attack.t1027
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

rule MALWARE_WIN_LETHIC_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Lethic 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 = "lethic" 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.

1. Sever network connectivity for the flagged endpoint to terminate persistent command-and-control (C2) communication channels and stop Lethic from retrieving secondary stage payloads.
2. Capture process memory triage to detect and terminate malicious threads injected by Lethic into legitimate system processes such as explorer.exe or svchost.exe.
3. Audit Windows Registry Run keys (HKCU\Software\Microsoft\Windows\CurrentVersion\Run) and Task Scheduler entries to locate and purge Lethic persistence hooks.
4. Deploy updated enterprise EDR detection signatures and conduct an out-of-band endpoint scan to isolate dropped binaries and staged payloads.
5. Rotate all credentials, domain user passwords, and session cookies active on the system during the Lethic execution timeframe.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

1. Do not assume the incident is resolved simply because an antivirus tool removed the initial Lethic dropper; always verify that secondary payloads and persistence hooks have been eradicated.
2. Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Lethic until memory triage is complete.
3. Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.

References & External Analysis

• Malpedia (Fraunhofer FKIE): Lethic (win.lethic)
• CISA Advisory: CISA Alert AA20-302A (Top Routinely Exploited Vulnerabilities)
• Search "lethic" on VirusTotal (External Analysis)
• Search "lethic" on Any.Run (Sandbox Sandbox)
• Search "lethic" on MalwareBazaar (Malware Samples)

North American Authority Advisory (CISA / NIST)

The Cybersecurity and Infrastructure Security Agency (CISA) has published an official US federal advisory on this family, which can be mapped to NIST Cybersecurity Framework (CSF) incident response controls: CISA Alert AA20-302A (Top Routinely Exploited Vulnerabilities) ↗

Frequently Asked Questions

Related Threats (Category: Spam Bot)

Explore other documented threats in the same operational category:

• Tofsee
• Kelihos
• Necurs

Machine-readable

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