Keyer
Table of Contents
Overview
Executive Summary
Keyer is a dedicated, malicious Keylogger and Information Stealer. Its primary objective is to silently monitor a victim's keystrokes, capturing passwords, personal communications, and sensitive financial data without the user's knowledge, and transmitting this harvested intelligence to remote cybercriminals.Infection Vector and Technical Capabilities
Keyer is typically distributed via spear-phishing campaigns containing malicious attachments, software bundling (hidden within "free" or cracked applications), or as a secondary payload dropped by an initial access broker. Once executed, Keyer establishes deep system hooks to monitor user input:- Keystroke Interception: The malware utilizes Windows API hooking (specifically utilizing `SetWindowsHookEx`) to intercept hardware interrupts from the keyboard. This allows it to record every single keystroke before it reaches the intended application.
- Contextual Logging: Advanced variants of Keyer do not just record raw keystrokes; they record the title of the active window where the keystrokes were entered. This allows attackers to easily parse the logs to find the specific keystrokes entered into "Bank of America Login" or "VPN Authentication."
- Exfiltration: The recorded logs are typically saved locally to a hidden, encrypted file. Periodically, the keylogger will silently transmit this file to an attacker-controlled server via SMTP (email), FTP, or HTTP POST requests.
Threat Assessment
A Keyer infection is a severe privacy and security breach. Because it captures data at the hardware input level, it completely bypasses the encryption of HTTPS websites and renders standard password complexity rules useless, as the attacker receives the password exactly as it is typed.Incident Response and Remediation
- Immediate Network Isolation: Isolate the machine to immediately halt the outbound transmission of the recorded keylogs.
- Complete Credential Reset: Assume that every password ever typed on the infected machine (including network domain credentials, personal banking, and social media) has been compromised. The user must initiate a comprehensive password reset from a known-secure, separate device.
- Endpoint Sweeps: Utilize robust EDR or anti-malware tools to locate and terminate the keylogger process. Pay close attention to hidden files in `%AppData%` and anomalous entries in the Registry `Run` keys used for persistence.
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 |
|---|---|---|---|
T1056.001 | Keylogging | Credential Access | ATT&CK ↗ |
T1114 | Email Collection (Harvesting addresses for spamming) | Collection | ATT&CK ↗ |
T1547.001 | Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder | Persistence | ATT&CK ↗ |
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.
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-MFA | Multi-factor Authentication | Harden | T1056.001 | Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless. |
D3-EAM | Email Access Monitoring | Detect | T1114 | Monitor Graph API and MAPI email harvesting routines and alert on bulk email downloads originating from unusual IP addresses. |
D3-RPM | Registry Persistence Monitoring | Detect | T1547.001 | Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management. |
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_KEYER_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Keyer"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "keyer" ascii wide nocase
$s2 = "trojan.keylogger.keyer" ascii wide nocase
$s3 = "spyware.keyer" ascii wide nocase
$s4 = "win32/keyer" 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 - Keyer (Advanced Threat) Execution & Triage
id: 18da94bf-e5aa-5008-a1a4-81b0b375d68e
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Keyer 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/keyer
- 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.advanced-threat
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1056_001
- attack.t1114
- attack.t1547_001
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
Tier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_KEYER_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Keyer 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 = "keyer" 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.
- Enforce forensic network isolation on all suspected endpoints while maintaining an out-of-band telemetry conduit to capture live Keyer adversary activity.
- Perform full memory dumps across identified staging nodes to extract memory-only implants, kernel rootkit hooks, and decrypted Keyer C2 infrastructure IP/domain lists.
- Review Active Directory domain controller authentication logs for anomalous Kerberos ticket requests (Pass-the-Ticket, Golden Ticket) and unauthorized DCSync operations associated with Keyer.
- Block all confirmed C2 domains, dynamic DNS endpoints, and proxy IP addresses across perimeter firewalls, proxies, and DNS security gateways.
- Conduct an enterprise-wide sweep across surrounding subnets for secondary webshells, WMI event subscriptions, or remote execution tooling left behind by Keyer operators.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not assume the incident is resolved simply because an antivirus tool removed the initial Keyer dropper; always verify that secondary payloads and persistence hooks have been eradicated.
- Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Keyer until memory triage is complete.
- Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.
References & External Analysis
- Search "keyer" on VirusTotal (External Analysis)
- Search "keyer" on Any.Run (Sandbox Sandbox)
- Search "keyer" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Keyer and what threat category does it belong to?
Keyer is classified as a Advanced Threat. 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 Keyer establish persistence and evade defensive controls?
Keyer 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 Keyer compromise?
Security teams responding to Keyer 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 lateral movement and credential access tactics does Trojan.Keylogger.Keyer leverage in enterprise intrusions?
Trojan.Keylogger.Keyer frequently utilizes privileged account harvesting techniques such as LSASS memory dumping, Kerberoasting, and token impersonation to escalate privileges. Once administrative credentials are acquired, it pivots across the victim network utilizing living-off-the-land binaries (LOLBins) such as WMI, PowerShell remoting, and PsExec, or abuses remote desktop protocols (RDP) to reach critical internal repositories and domain controllers.
How does Trojan.Keylogger.Keyer maintain covert communications and evade perimeter network monitoring?
Trojan.Keylogger.Keyer often relies on multi-stage command and control (C2) architectures utilizing encrypted protocols over standard web ports (HTTPS/443 or DNS tunneling) to blend in with legitimate enterprise network traffic. Many variants incorporate proxy networks, domain fronting, or cloud services (such as Microsoft Graph API, Google Drive, or Telegram) to masquerade C2 channels, bypassing traditional signature-based egress filtering.
How do I remove the Keyer Advanced_Threat from Windows?
Manual removal of Keyer 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 Keyer a virus or a Advanced_Threat?
Keyer is classified as a Advanced_Threat. Unlike traditional viruses that infect files, modern malware like Keyer typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Keyer infection?
Symptoms of Keyer 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 Advanced_Threats
Want to prevent Keyer and similar threats from compromising your organization? Read our comprehensive defensive guide: Think You've Been Hacked? What To Do First.
📣 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/keyer.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.