huntrule

Windows Registry Run Key Autorun Entries Targeting Kapeka Backdoor

Flags Windows Run key registry changes whose data matches a Kapeka-style rundll32 .wll (#1) autorun entry.

FreeReviewedSigma · High · v5
Product
windows
Category
registry_set
Author
Swachchhanda Shrawan Poudel (SigmaHQ), DRL 1.1
Published
2024-07-03
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Persistence → Priv Esc

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags creation or modification of Windows registry autorun values under the CurrentVersion\Run location where the value name ends with specific Kapeka-related strings. It matches entries that reference rundll32.exe with a .wll payload and a #1 parameter, consistent with backdoor persistence behavior. The detection relies on Windows registry set telemetry capturing TargetObject and Details fields for the value being written.

Reporting behind it

Related detections9 linkedT1547.001 — drag to rearrange
Suspicious SystemBC Persistence via Run Key to ProgramData Script
Suspicious Interlock RAT Persistence via HKCU Run Key Registration to AppData Payload (via process_creation)
Suspicious SOCKS Proxy Persistence via SystemBC PowerShell Run Key
Suspicious Run Key Persistence Referencing PowerShell Script via registry_set
Malicious Startup Persistence via WindowsDefenderSync Shortcut (via file_event)
Malicious PXA Stealer Persistence via Windows Update Service Run Key (via registry_set)
Suspicious NetSupport client32 Persistence via Run Key from ProgramData
Suspicious Run Key Persistence Named NvidiaDriverUpdate (via registry_set)
Suspicious HTA File Dropped into Startup Folder
Windows Registry Run Key Autorun Entries Targeting Kapeka Backdoor
Pivot detection · T1547.001 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. 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.