Lamer

Overview

Worm:Win32/Lamer is a dual-threat propagation worm and trojan downloader that emerged in the mid-2000s, designed to infiltrate Windows networks and establish a persistent beachhead for secondary crimeware deployment. Spreading through peer-to-peer (P2P) file-sharing networks, infected removable storage devices, and open Windows network shares, Lamer copies itself using deceptive filenames mimicking popular cracked utilities, media files, and system tools. Once executed, Lamer profiles the host environment (collecting operating system version, domain roles, and security software indicators), modifies registry Run keys to survive reboots, and connects to remote C2 infrastructure to download second-stage infostealers and ransomware droppers.

Known aliases

Threat reports may refer to this family under multiple names:

• Lamer
• Worm:Win32/Lamer
• W32/Lamer
• Trojan.Lamer
• Worm.Win32.Lamer
• Backdoor.Lamer

Threat Actor Attribution

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

• Underground Cybercrime Groups High confidence
  Basis:

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: Lamer.A · Lamer.B Network Spreader · Lamer Downloader

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.
• T1105: Implement network intrusion detection systems (NIDS) and host-based firewalls to block unauthorized inbound or outbound file transfers.

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-2004-0115 — In-depth exploitation analysis and catalog intelligence (NIST NVD ↗).
• CVE-2008-4250 — 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.

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.

• 2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b3c
• 3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b3c4d

Delivery vectors

• p2p_file_sharing_networks
• compromised_shared_folders

Persistence mechanisms

• HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
• Scheduled Tasks

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_LAMER_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Lamer"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "lamer" ascii wide nocase
        $s2 = "lamer" ascii wide nocase
        $s3 = "worm:win32/lamer" ascii wide nocase
        $s4 = "w32/lamer" ascii wide nocase
        $s5 = "trojan.lamer" ascii wide nocase
        $s6 = "worm.win32.lamer" ascii wide nocase
        $s7 = "backdoor.lamer" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Lamer (Worm) Execution & Triage
id: 0e68fa2a-5efc-597c-a185-17157999b39e
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Lamer 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/lamer
- 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.t1105
- attack.t1547_001
- attack.t1082
- attack.t1059_003
- attack.t1071_001
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_LAMER_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Lamer 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 = "lamer" 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. Isolate compromised endpoints to stop secondary malware downloads and lateral network worm scanning.
2. Remove unauthorized autorun registry entries and inspect scheduled tasks for suspicious binaries.
3. Scan and disinfect local network shares and remove deceptive executable files mimicking media tools.
4. Ensure endpoints are fully patched against historical Windows SMB vulnerabilities.

What to Avoid

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

1. Do not allow unmonitored peer-to-peer file sharing applications within enterprise corporate networks.
2. Avoid executing unverified application installers or keygens downloaded from public forums.
3. Never grant write permissions to unauthenticated users on internal organizational file shares.

References & External Analysis

• Microsoft Security Intelligence: Worm:Win32/Lamer Technical Summary
• Symantec Security Response: Trojan.Lamer Analysis
• NIST National Vulnerability Database CVE-2008-4250
• Search "lamer" on VirusTotal (External Analysis)
• Search "lamer" on Any.Run (Sandbox Sandbox)
• Search "lamer" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Worm)

Explore other documented threats in the same operational category:

• Mydoom
• Ngrbot
• Blasterx
• Mogoogwi
• Koobface
• Xorer
• Blaster
• Mira

Machine-readable

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