Keydoor

Overview

Executive Summary

Infection Vector and Technical Capabilities

• Covert Backdoor Access: Keydoor establishes a persistent, encrypted connection to a remote command-and-control (C2) server. Unlike noisy botnets, it often "beacons" infrequently (e.g., once every 24 hours) to evade detection by edge firewalls and network anomaly monitoring. This backdoor allows the attacker to silently upload secondary modules, exfiltrate data, or open an interactive remote shell.
• Deep Keylogging (API Hooking): The malware implements a sophisticated keylogger by hooking deep into the Windows API (e.g., using `SetWindowsHookEx` or even kernel-mode drivers). This allows it to intercept keystrokes across all applications, specifically targeting web browsers, password managers, and enterprise SSO portals.
• Clipboard and Screen Capture: To supplement keylogging, Keydoor frequently monitors the system clipboard (stealing copied passwords or cryptocurrency addresses) and takes periodic screenshots of the active desktop.

Threat Assessment

Incident Response and Remediation

• Immediate Network Isolation: Isolate the infected endpoint from the LAN immediately to sever the backdoor connection and halt data exfiltration.
• Comprehensive Credential Reset: Assume all credentials utilized on the infected machine, as well as any stored in browsers or password managers, are fully compromised. Initiate an immediate, organization-wide password reset.
• Forensic Memory Analysis: Because Keydoor relies heavily on API hooking, perform memory forensics (using tools like Volatility) to identify the specific hooks and extract the C2 configuration from volatile memory before rebooting the system.

Known aliases

Threat reports may refer to this family under multiple names:

• Trojan.Keydoor
• Backdoor.Keydoor
• Keylogger.Win32.Keydoor

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:

• T1056.001: Implement Endpoint Detection and Response (EDR) to monitor for suspicious API calls related to keystroke interception. Enforce Multi-Factor Authentication (MFA) to render stolen passwords useless.
• T1059: Restrict execution of scripting languages such as PowerShell, VBScript, or Python to authorized administrators. Enforce Script Block Logging.
• T1113: Monitor for frequent or unauthorized screen captures or clipboard reads. Restrict background applications from accessing desktop APIs.

MITRE D3FEND™ Defensive Countermeasures

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

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

title: SystemHelpDesk Detection - Keydoor (Backdoor) Execution & Triage
id: 8ea0056d-a998-595a-ae5c-5bc50170ed31
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Keydoor malware family. Detects proxy execution, reflective DLL loading,
  and remote command injection associated with modular enterprise backdoors.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/keydoor
- 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.backdoor
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1056_001
- attack.t1059
- attack.t1113
- attack.t1115
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \powershell.exe
    - \cmd.exe
    - \rundll32.exe
    - \regsvr32.exe
    CommandLine|contains:
    - DownloadString
    - IEX(
    - '/s /n /u /i:'
    - sc create
    - start-process
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high

rule MALWARE_WIN_KEYDOOR_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Keydoor 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 = "keydoor" 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. Immediately isolate the compromised host from internal LAN and WAN environments to cut off interactive remote shell sessions established by Keydoor.
2. Inspect active socket listeners and outbound established network connections ('netstat -ano') to identify and sever covert TCP/UDP channels used by Keydoor.
3. Scan Windows Services, Scheduled Tasks, and Startup folders to locate and eliminate persistent backdoor listeners configured by Keydoor.
4. Invalidate all active VPN profiles, local administrator credentials, and session tokens that may have been harvested by the Keydoor operator.
5. Re-image the affected host using a validated golden image prior to reconnecting it to enterprise network segments.

What to Avoid

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

1. Do not attempt to interact with or send messages through the Keydoor remote terminal, as this alerts the attacker and may cause them to execute destructive anti-forensic commands.
2. Avoid relying solely on static file signatures, as Keydoor payloads frequently execute reflectively in memory without writing binaries to disk.

References & External Analysis

• Search "keydoor" on VirusTotal (External Analysis)
• Search "keydoor" on Any.Run (Sandbox Sandbox)
• Search "keydoor" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Backdoor)

Explore other documented threats in the same operational category:

• Opanki
• Netstream
• Werpoapt
• Winvnc
• Winnti
• Zxshell
• Teamviewer
• Shodi

Machine-readable

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