Laqma

Category: trojan · Aliases: TrojanSpy:Win32/Laqma.B, VirTool:WinNT/Laqma.C, Trojan:Win32/Laqma, Troj/Laqma-A, Win32/Laqma · Sample count (EMBER 2018): 204 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: TrojanStatus: Automated SignaturePlatform: WINDOWS_PEStage: Collection, Defense Evasion, PersistenceFirst seen: 2008Actor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Information Theft🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 7
Executive Summary
Laqma (cataloged across security vendors as TrojanSpy:Win32/Laqma.B, VirTool:WinNT/Laqma.C, and Trojan:Win32/Laqma) is an evasive Windows trojan-spy and rootkit utility discovered in 2008.

Table of Contents

Overview

Laqma (cataloged across security vendors as TrojanSpy:Win32/Laqma.B, VirTool:WinNT/Laqma.C, and Trojan:Win32/Laqma) is an evasive Windows trojan-spy and rootkit utility discovered in 2008. Spread through malicious spam email attachments, compromised websites, and pirate software cracks, Laqma is engineered for covert surveillance and long-term backdoor access. A key technical feature of Laqma is its deployment of a kernel-mode rootkit driver (typically dropped as lanmandrv.sys and registered under the Windows Service LanManDrv). This driver hooks low-level kernel APIs to conceal Laqma's executable processes, disk files, registry entries, and active network connections from Windows task managers and endpoint security products. Operating in the background, Laqma harvests sensitive system telemetry, logs user credentials, intercepts network communications, and connects to remote command-and-control servers to download secondary malicious binaries.

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:

Derived From / Upstream Ancestry: Winnt Kernel Rootkit Framework · Trojan-Spy Information Stealer Engine

Known Derivatives & Downstream Variants: Laqma.A · Laqma.B · Laqma.C

MITRE ATT&CK Techniques

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

→ 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-KMCKernel Memory Integrity CheckingHardenT1014Enable Hypervisor-Protected Code Integrity (HVCI) and UEFI Secure Boot to prevent unsigned kernel driver execution.
D3-EAFEgress Analysis and FilteringIsolateT1041Enforce perimeter TLS inspection and alert on anomalous outbound data volume ratios transmitting over active C2 channels.
D3-MFAMulti-factor AuthenticationHardenT1056.001Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless.
D3-NTINetwork Traffic InspectionDetectT1105Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols.
D3-SCMWindows Service Creation MonitoringDetectT1543.003Verify service binary image signatures and restrict standard users from creating or modifying service definitions.

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_LAQMA_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Laqma"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "laqma" ascii wide nocase
        $s2 = "trojanspy:win32/laqma.b" ascii wide nocase
        $s3 = "virtool:winnt/laqma.c" ascii wide nocase
        $s4 = "trojan:win32/laqma" ascii wide nocase
        $s5 = "troj/laqma-a" ascii wide nocase
        $s6 = "win32/laqma" 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 - Laqma (Trojan) Execution & Triage
id: 6b33fb79-6799-5d01-98f6-2e30f7b25848
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Laqma 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/laqma
- https://malware-families-catalog.systemhelpdesk.com/defensive/downloader-dropper-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.trojan
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1056_001
- attack.t1543_003
- attack.t1014
- attack.t1105
- attack.t1041
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_LAQMA_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Laqma 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 = "laqma" 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)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

  1. Isolate the endpoint from the network to stop ongoing credential exfiltration.
  2. Use an offline boot disk or Windows Defender Offline scan to detect and remove the kernel rootkit driver (lanmandrv.sys).
  3. Delete the rogue Windows Service entry 'LanManDrv' from HKLM\System\CurrentControlSet\Services.
  4. Force immediate enterprise-wide password resets for all accounts accessed on the infected workstation.

What to Avoid

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

  1. Do not rely solely on user-mode task managers during triage, as the kernel rootkit actively hides malicious processes.
  2. Avoid running executable files obtained from unverified software crack portals.

References & External Analysis

Frequently Asked Questions

What is the Laqma trojan family?

Laqma is an evasive Windows trojan-spy and kernel-level rootkit designed for credential theft and backdoor access.

How does Laqma hide its presence on Windows?

It installs a kernel-mode rootkit driver (LanManDrv / lanmandrv.sys) that hooks system APIs to hide processes and files.

What surveillance capabilities does Laqma have?

It captures keystrokes, harvests stored system credentials, intercepts network packets, and logs system telemetry.

How does Laqma spread to target endpoints?

It is distributed through spear-phishing emails, compromised software crack sites, and drive-by download vectors.

How can Laqma rootkit infections be mitigated?

Boot into Windows Recovery or offline scanner to delete lanmandrv.sys, purge the service key, and rotate compromised passwords.

How do I remove the Laqma Trojan from Windows?

Manual removal of Laqma 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 Laqma a virus or a Trojan?

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

What are the main symptoms of a Laqma infection?

Symptoms of Laqma 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 Trojans

Want to prevent Laqma and similar threats from compromising your organization? Read our comprehensive defensive guide: Banking Trojan Protection for Businesses.

📣 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/laqma.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.