Windows Process Creation: Sticky Keys Backdoor via sethc.exe Replacement

Flags forced replacement of C:\Windows\System32\sethc.exe with cmd.exe consistent with a Sticky Keys backdoor.

FreeReviewedSigma · Critical · v2
Product
windows
Category
process_creation
Author
Sreeman (SigmaHQ), DRL 1.1
Published
2020-02-18
Updated
2026-07-31

ATT&CK techniques

Persistence → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule matches a command line that copies cmd.exe over sethc.exe using overwrite flags, which is consistent with a sticky keys backdoor persistence technique that grants privileged console access. Attackers use this to trigger a privileged shell through accessibility shortcut behavior without providing additional authentication. The detection relies on Windows process creation telemetry with full command-line content containing the specific copy sequence to sethc.exe.

Related detections9 linkedT1546.008 — drag to rearrange
Malicious Sticky Key File Created from CMD Copy (via file_event)
Malicious Stickey Key Called CMD via Command Execution - Hash Detection (via process_creation)
Malicious Stickey Key IFEO Registry Changed - Reg via Sysmon (via registry_event)
Malicious Accessibility Feature Backdoor via Image File Execution Options Debugger (via registry_set)
Malicious Stickey Key Called CMD via Command Execution (via process_creation)
Malicious Sticky Key Sethc Command for Replacement by CMD (via process_creation)
Malicious Stickey Key IFEO - Reg via Command (via process_creation)
Malicious Accessibility Feature Debugger Hijack via IFEO (via registry_set)
Windows Privilege Escalation via mklink Symlink Between cmd.exe and osk.exe
Windows Process Creation: Sticky Keys Backdoor via sethc.exe Replacement
Pivot detection · T1546.008 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.