Malicious BabyLockerKZ Run Key Persistence

PremiumReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-09-12
Updated
2026-09-12

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 detects creation of a CurrentVersion Run value named BabyLockerKZ. This MedusaLocker variant registered a BabyLockerKZ autorun entry to persist across reboots. A Run key carrying the malware family name is a direct persistence indicator tying host activity to this ransomware operation.

Related detections9 linkedT1547.001 — drag to rearrange
Suspicious Autorun Registry Persistence via sausageLoop Run Key
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
Suspicious RoboForm Update Run Key Masquerade (via registry_set)
Malicious BabyLockerKZ Run Key Persistence
Pivot detection · T1547.001 · 9 related

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