Keyboarddisable

Overview

Executive Summary

Technical Implementation and Context

• API Hooking: Utilizing `SetWindowsHookEx` with the `WH_KEYBOARD_LL` (Low-Level Keyboard Hook) parameter to intercept all keystrokes. The malicious hook function simply discards the input, preventing it from reaching any application or the OS.
• Driver Manipulation: In more sophisticated attacks (often requiring kernel-level privileges), the malware may attempt to uncouple or corrupt the legitimate keyboard filter drivers (`kbdclass.sys`).

Threat Assessment

Incident Response and Recovery

• Hard Reboot and Safe Mode: If the keyboard is disabled by user-mode hooking, a hard reboot followed immediately by booting into Windows Safe Mode (which loads minimal drivers and startup programs) will often bypass the malicious hook.
• Remote Administration: System administrators can utilize remote management tools (RDP, PowerShell Remoting, or enterprise EDR consoles) to identify and kill the offending process, as the remote keyboard input may bypass local hooks.
• Root Cause Analysis: Treat the disabled keyboard as a symptom of a larger infection. Once control is regained, a full forensic scan must be performed to locate the primary payload (e.g., the ransomware or trojan) that deployed the KeyboardDisable component.

Known aliases

Threat reports may refer to this family under multiple names:

• Trojan.KeyboardDisable
• ScreenLocker Component
• Behavior.KeyboardLock

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.

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

title: SystemHelpDesk Detection - Keyboarddisable (Ransomware) Execution & Triage
id: 8040e349-e91b-5653-84eb-4df0f1ffaea9
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Keyboarddisable 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/keyboarddisable
- 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.t1489
- attack.t1056_001
- attack.t1486
- attack.t1490
- attack.t1082
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: critical

rule MALWARE_WIN_KEYBOARDDISABLE_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Keyboarddisable 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 = "keyboarddisable" 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 affected host(s) from the internal network (disconnect physical Ethernet and disable Wi-Fi/Bluetooth) to prevent Keyboarddisable from spreading laterally or encrypting network-attached storage (NAS) and shared SMB volumes.
2. Preserve volatile system memory (RAM capture) on a representative endpoint before attempting a reboot or power-down, as Keyboarddisable symmetric encryption keys or uncompiled payload components may still reside in memory.
3. 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 Keyboarddisable to inhibit recovery.
4. 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.
5. Restore critical assets and databases exclusively from verified, air-gapped, or immutable offline backups once the Keyboarddisable 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.

1. Do not restart or power cycle infected systems prematurely; doing so destroys volatile RAM encryption keys and may trigger bootloader locking logic embedded in Keyboarddisable.
2. Avoid negotiating or paying the extortion demand without prior forensic evaluation and consultation with incident response specialists, as payment does not guarantee data recovery.
3. Do not connect clean backup drives or external storage to the affected network until Keyboarddisable eradication is completely verified.

References & External Analysis

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

Frequently Asked Questions

Related Threats (Category: Ransomware)

Explore other documented threats in the same operational category:

• Smee
• Diss
• Excrevie
• Tinclex
• Udslee
• Sasquor
• Offend
• Etap

Machine-readable

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