Liudoor
Table of Contents
Overview
Executive Summary
Liudoor is a malicious Backdoor Trojan designed to covertly infiltrate Windows systems, establish stealthy persistence, and provide a remote attacker with unfettered, unauthorized access to the compromised machine. Unlike simple downloaders, a backdoor allows the threat actor to directly interact with the system, execute arbitrary commands, and manually exfiltrate sensitive data.Infection Vector and Technical Capabilities
Liudoor is typically distributed through targeted spear-phishing campaigns containing malicious attachments (often macro-enabled Office documents or weaponized PDFs) or by exploiting unpatched vulnerabilities in public-facing web servers or RDP (Remote Desktop Protocol) endpoints. Once executed, Liudoor focuses on establishing a secure, persistent connection to the attacker:- Command and Control (C2) Communication: The backdoor establishes a connection to a remote C2 server, often over encrypted channels (HTTPS) or via custom protocols on non-standard ports to evade Intrusion Detection Systems (IDS). It actively "listens" for incoming commands.
- Remote Code Execution (RCE): The core functionality of Liudoor is to provide a remote shell. The attacker can execute arbitrary system commands (`cmd.exe` or PowerShell), upload or download files, and manipulate the Windows Registry at will.
- Lateral Movement Facilitation: Because the attacker has interactive control, Liudoor is frequently used as a "beachhead." The attacker will use the compromised host to scan the internal network, dump local credentials (using tools like Mimikatz), and pivot to more valuable servers or Domain Controllers.
Threat Assessment
A Liudoor infection is a critical security incident. The presence of an active backdoor means the network perimeter has completely failed, and a human adversary currently has interactive access to the internal network. Data exfiltration or the deployment of enterprise-wide ransomware is often imminent.Incident Response and Remediation
- Immediate Isolation: The highest priority is to physically disconnect the infected machine from the network to sever the attacker's interactive connection and prevent further lateral movement. Do not power off the machine, as volatile memory (RAM) is required for forensic analysis.
- Forensic Triage: Utilize Endpoint Detection and Response (EDR) or memory forensics to identify the specific processes associated with Liudoor, analyze its network connections to identify the C2 infrastructure, and determine if local administrator credentials have been dumped.
- Enterprise Password Reset and Re-imaging: Because the attacker had interactive access, all credentials used on or accessible from the compromised endpoint must be reset immediately. The endpoint itself must undergo a complete bare-metal wipe and re-image from a trusted baseline.
Known aliases
Threat reports may refer to this family under multiple names:
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 |
|---|---|---|---|
T1059.003 | Command and Scripting Interpreter: Windows Command Shell | Execution | ATT&CK ↗ |
T1105 | Ingress Tool Transfer | Command and Control | ATT&CK ↗ |
T1573.001 | Encrypted Channel: Symmetric Cryptography | Command and Control | ATT&CK ↗ |
T1021 | Remote Services (Lateral movement to critical bank infrastructure) | Lateral Movement | ATT&CK ↗ |
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.
- 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):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-PBA | Process Spawn Analysis | Detect | T1059.003 | Inspect command-line arguments and anomalous parent-child relationships spawning from cmd.exe. |
D3-NTI | Network Traffic Inspection | Detect | T1105 | Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols. |
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_LIUDOOR_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Liudoor"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "liudoor" ascii wide nocase
$s2 = "backdoor.liudoor" ascii wide nocase
$s3 = "trojan.liudoor" ascii wide nocase
$s4 = "win32/liudoor" 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 - Liudoor (Ransomware) Execution & Triage
id: 90421dfc-6671-586f-bc48-051f74729afc
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Liudoor malware family. Detects volume shadow copy deletion, boot status
tampering, and recovery inhibition characteristic of modern ransomware operations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/liudoor
- 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.ransomware
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1059_003
- attack.t1105
- attack.t1573_001
- attack.t1021
logsource:
category: process_creation
product: windows
detection:
selection_process:
Image|endswith:
- \vssadmin.exe
- \wmic.exe
- \wbadmin.exe
- \bcdedit.exe
CommandLine|contains:
- delete shadows
- shadowcopy delete
- resize shadowstorage
- recoveryenabled no
- ignoreallfailures
condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: criticalTier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_LIUDOOR_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Liudoor 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 = "liudoor" 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.
- Immediately isolate affected host(s) from the internal network (disconnect physical Ethernet and disable Wi-Fi/Bluetooth) to prevent Liudoor from spreading laterally or encrypting network-attached storage (NAS) and shared SMB volumes.
- Preserve volatile system memory (RAM capture) on a representative endpoint before attempting a reboot or power-down, as Liudoor symmetric encryption keys or uncompiled payload components may still reside in memory.
- Audit process execution logs and terminate active scripting interpreters (e.g. PowerShell, CMD, WScript) or commands executing 'vssadmin.exe delete shadows' or 'wbadmin' used by Liudoor to inhibit recovery.
- Investigate the initial compromise vector (such as exposed RDP instances, spearphishing attachments, or vulnerable edge gateways) and enforce an immediate credential reset for all compromised Active Directory accounts.
- Restore critical assets and databases exclusively from verified, air-gapped, or immutable offline backups once the Liudoor binary and related persistence hooks are eradicated.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not restart or power cycle infected systems prematurely; doing so destroys volatile RAM encryption keys and may trigger bootloader locking logic embedded in Liudoor.
- Avoid negotiating or paying the extortion demand without prior forensic evaluation and consultation with incident response specialists, as payment does not guarantee data recovery.
- Do not connect clean backup drives or external storage to the affected network until Liudoor eradication is completely verified.
References & External Analysis
- Search "liudoor" on VirusTotal (External Analysis)
- Search "liudoor" on Any.Run (Sandbox Sandbox)
- Search "liudoor" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Liudoor and what threat category does it belong to?
Liudoor is classified as a Ransomware. 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 Liudoor establish persistence and evade defensive controls?
Liudoor 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 Liudoor compromise?
Security teams responding to Liudoor 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 cryptographic algorithms and file targeting techniques does Backdoor.Liudoor employ during execution?
Backdoor.Liudoor typically leverages hybrid cryptographic architectures combining symmetric stream or block ciphers (such as AES-256 or ChaCha20) for rapid file encryption with asymmetric algorithms (such as RSA-2048 or Curve25519) to securely protect the session keys. It aggressively targets sensitive file extensions including corporate documents, databases, virtual disks, and backups while systematically executing commands to delete Volume Shadow Copies (vssadmin delete shadows /all /quiet) and disable system recovery options.
Are decryptors available for Backdoor.Liudoor, and what is the recommended recovery procedure?
Decryption availability for Backdoor.Liudoor depends on whether security researchers or law enforcement (such as the No More Ransom initiative) have recovered the master private keys or discovered flaws in its key generation routines. Victims should never pay the extortion demand, as payment fuels criminal operations without guaranteeing file restoration. The recommended recovery procedure entails isolating infected hosts, conducting forensic disk imaging, identifying the root access vector, and restoring validated systems from immutable offline backups.
How do I remove the Liudoor Ransomware from Windows?
Manual removal of Liudoor 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 Liudoor a virus or a Ransomware?
Liudoor is classified as a Ransomware. Unlike traditional viruses that infect files, modern malware like Liudoor typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Liudoor infection?
Symptoms of Liudoor 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 Ransomwares
Want to prevent Liudoor and similar threats from compromising your organization? Read our comprehensive defensive guide: Ransomware Containment & Incident Response.
📣 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/liudoor.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.