{
  "family": "keyboarddisable",
  "sample_count": 1,
  "category": "ransomware",
  "description": "<h3>Executive Summary</h3>\n\"KeyboardDisable\" is not a fully-featured malware family, but rather a specific, malicious payload component or behavioral symptom often associated with ransomware, screenlockers, or disruptive trojans. As the name suggests, its primary function is to intercept or completely disable keyboard input, severely hindering the victim's ability to respond to a cyberattack.\n\n<h3>Technical Implementation and Context</h3>\nThe ability to disable keyboard (and often mouse) input is a tactic utilized during the critical execution phases of other malware. It is implemented using native operating system APIs.\n\nIn a Windows environment, this is typically achieved by:\n<ul>\n<li><strong>API Hooking:</strong> 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.</li>\n<li><strong>Driver Manipulation:</strong> In more sophisticated attacks (often requiring kernel-level privileges), the malware may attempt to uncouple or corrupt the legitimate keyboard filter drivers (`kbdclass.sys`).</li>\n</ul>\nThis tactic is most frequently observed in \"Screenlocker\" ransomware (which locks the screen and demands payment without necessarily encrypting files) to prevent the user from accessing the Task Manager (Ctrl+Alt+Del) or booting into Safe Mode.\n\n<h3>Threat Assessment</h3>\nWhile disabling the keyboard does not destroy data, it is a severe Denial of Service (DoS) condition on the local endpoint. It induces panic and forces the user to perform a hard reset, which may exacerbate data loss if ransomware is actively encrypting files in the background.\n\n<h3>Incident Response and Recovery</h3>\n<ul>\n<li><strong>Hard Reboot and Safe Mode:</strong> 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.</li>\n<li><strong>Remote Administration:</strong> 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.</li>\n<li><strong>Root Cause Analysis:</strong> 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.</li>\n</ul>",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [
    "Trojan.KeyboardDisable",
    "ScreenLocker Component",
    "Behavior.KeyboardLock"
  ],
  "enrichment_level": "expert-seo",
  "faq": [
    {
      "@type": "Question",
      "name": "What is Keyboarddisable and what threat category does it belong to?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Keyboarddisable 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."
      }
    },
    {
      "@type": "Question",
      "name": "How does Keyboarddisable establish persistence and evade defensive controls?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Keyboarddisable 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."
      }
    },
    {
      "@type": "Question",
      "name": "What are the essential incident response steps for mitigating a Keyboarddisable compromise?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Security teams responding to Keyboarddisable 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."
      }
    },
    {
      "@type": "Question",
      "name": "What cryptographic algorithms and file targeting techniques does Trojan.KeyboardDisable employ during execution?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Trojan.KeyboardDisable 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."
      }
    },
    {
      "@type": "Question",
      "name": "Are decryptors available for Trojan.KeyboardDisable, and what is the recommended recovery procedure?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Decryption availability for Trojan.KeyboardDisable 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."
      }
    }
  ],
  "faq_count": 5,
  "mitre_attack": [
    "T1489",
    "T1056.001",
    "T1486",
    "T1490",
    "T1082",
    "T1027"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-10-15",
  "type": "Trojan",
  "target_industries": [
    "Healthcare",
    "Critical Infrastructure",
    "Enterprise"
  ],
  "motivation": "Financial Extortion",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ],
  "attack_stage": [
    "defense_evasion",
    "impact"
  ],
  "ecosystem": [
    "windows_pe"
  ],
  "is_emerging": false,
  "mitre_attack_detail": [
    {
      "id": "T1489",
      "name": "Service Stop (Forcefully stopping AV services)",
      "tactic": "Impact"
    },
    {
      "id": "T1056.001",
      "name": "Keylogging",
      "tactic": "Credential Access"
    },
    {
      "id": "T1486",
      "name": "Data Encrypted for Impact",
      "tactic": "Impact"
    },
    {
      "id": "T1490",
      "name": "Inhibit System Recovery (Behaviorally blocking the deletion of backups)",
      "tactic": "Impact"
    },
    {
      "id": "T1082",
      "name": "System Information Discovery",
      "tactic": "Discovery"
    },
    {
      "id": "T1027",
      "name": "Obfuscated Files or Information",
      "tactic": "Defense Evasion"
    }
  ],
  "containment_steps": [
    "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.",
    "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.",
    "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.",
    "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 Keyboarddisable binary and related persistence hooks are eradicated."
  ],
  "what_to_avoid": [
    "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.",
    "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 Keyboarddisable eradication is completely verified."
  ],
  "target_platforms": [
    "Windows 11",
    "Windows 10",
    "Windows Server 2022",
    "Windows Server 2019"
  ]
}