Lost_Door

Category: rat · Aliases: Backdoor.LostDoor, Trojan.Win32.LostDoor, Backdoor:Win32/LostDoor, Win32/LostDoor.RAT, LostDoor.E-Server · Sample count (EMBER 2018): 0 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: RatSeverity: MEDIUMStatus: Automated SignaturePlatform: WINDOWS_PEStage: Initial Access, ExecutionFirst seen: 2007Motivation: Espionage🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
Lost Door (cataloged across security software as Backdoor.LostDoor, Trojan.Win32.LostDoor, and Backdoor:Win32/LostDoor) is a classic Delphi-authored Remote Access Trojan (RAT) created in 2007 by an underground developer known as 'Türkojan' / 'Lost_Door'.

Table of Contents

Overview

Lost Door (cataloged across security software as Backdoor.LostDoor, Trojan.Win32.LostDoor, and Backdoor:Win32/LostDoor) is a classic Delphi-authored Remote Access Trojan (RAT) created in 2007 by an underground developer known as 'Türkojan' / 'Lost_Door'. Widely adopted across global cybercriminal forums, Lost Door provides full remote administrative control over compromised Windows endpoints. Its capabilities include real-time desktop screen capture, webcam surveillance, audio recording, reverse command shells, registry editing, active process management, and automated password extraction from web browsers, email clients, and instant messengers. Lost Door was commonly distributed through peer-to-peer file sharing networks, malicious email attachments, and trojanized freeware software bundles.

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: Delphi Rat Frameworks

Known Derivatives & Downstream Variants: Lost Door V6.0 · Lost Door V8.0 · Lost Door Fly Edition

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-MFAMulti-factor AuthenticationHardenT1056.001Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless.
D3-PBAProcess Spawn AnalysisDetectT1059.003Inspect command-line arguments and anomalous parent-child relationships spawning from cmd.exe.
D3-WAFWeb Content Filtering & InspectionFilterT1071.001Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles.
D3-SDScreen Capture DetectionDetectT1113Monitor desktop graphics API calls (BitBlt, GetDC) triggered by non-standard background threads.
D3-HACHardware Device Access ControlIsolateT1125Enforce Group Policy hardware access restrictions on integrated webcams and microphones.
D3-RPMRegistry Persistence MonitoringDetectT1547.001Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management.

Exploited Vulnerabilities (CVEs)

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

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_LOST_DOOR_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Lost_Door"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "lost_door" ascii wide nocase
        $s2 = "backdoor.lostdoor" ascii wide nocase
        $s3 = "trojan.win32.lostdoor" ascii wide nocase
        $s4 = "backdoor:win32/lostdoor" ascii wide nocase
        $s5 = "win32/lostdoor.rat" ascii wide nocase
        $s6 = "lostdoor.e-server" 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 - Lost_door (Rat) Execution & Triage
id: 4780a5f4-5fbb-58f3-9985-031cfc4ddfc5
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Lost_door malware family. Detects unauthorized persistence creation via
  Windows Registry Run keys, scheduled tasks, and privilege escalation indicative
  of RAT installations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/lost_door
- 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.rat
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1056_001
- attack.t1113
- attack.t1125
- attack.t1123
- attack.t1059_003
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \reg.exe
    - \schtasks.exe
    - \cmd.exe
    - \powershell.exe
    CommandLine|contains:
    - \CurrentVersion\Run
    - /create /tn
    - bypass -enc
    - net user /add
    - net localgroup administrators
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_LOST_DOOR_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Lost_Door 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 = "lost_door" 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 compromised endpoints to cut active remote command sessions and stop live webcam/desktop streaming.
  2. Kill active Lost Door server processes and remove autostart entries.
  3. Purge persistence registry entries located under HKLM and HKCU Run keys.
  4. Perform an enterprise-wide password reset for all user accounts accessed from 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 execute software downloaded from unverified peer-to-peer file sharing repositories or forum links.
  2. Avoid continuing operation of a compromised endpoint without thorough forensic memory triage.

References & External Analysis

Frequently Asked Questions

What is the Lost Door remote access trojan?

Lost Door is a modular Delphi Remote Access Trojan developed in 2007 providing full interactive surveillance and remote control.

What surveillance modules are included in Lost Door?

Modules include live webcam capture, microphone eavesdropping, keystroke logging, screen viewing, and password theft.

How was Lost Door propagated across victim systems?

It was distributed through peer-to-peer file sharing networks, IRC chat file transfers, and trojanized gaming cracks.

Which CVE vulnerabilities have been linked to Lost Door delivery?

Campaigns delivering Lost Door droppers have exploited shortcut and document flaws including CVE-2010-2568 and CVE-2012-0158.

How can systems be defended against Lost Door?

Enforce firewall egress filtering, deploy endpoint antimalware protection, and monitor registry Run keys and active sockets.

How do I remove the Lost_Door Rat from Windows?

Manual removal of Lost_Door 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 Lost_Door a virus or a Rat?

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

What are the main symptoms of a Lost_Door infection?

Symptoms of Lost_Door 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 Rats

Want to prevent Lost_Door and similar threats from compromising your organization? Read our comprehensive defensive guide: Backdoor & RAT 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/lost_door.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.