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 Autorun Registry Persistence via sausageLoop Run Key
Malicious BabyLockerKZ Run Key Persistence
Suspicious Run Key Persistence Pointing To User-Writable Path
Malicious Ctrlpanel Run Key Autostart Persistence (via registry_set)
Persistence Run Key Pointing to svchost.exe in AppData Roaming
URL Shortcut File Created in Startup Folder for Persistence
Suspicious Run Key Persistence via UpdateCheck Value in Operation TrueChaos
Suspicious Run Key Persistence Pointing to AppData Local Copy
Malicious WezRat Persistence via Chrome Updater Run Key
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.