Suspicious Rootkit Configuration Registry Keys (via registry_set)

PremiumReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-10-25
Updated
2026-10-25

ATT&CK techniques

Persistence → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Priv Esc

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects registry values written under SOFTWARE keys prefixed with the distinctive nya marker. The OBSCURE#BAT campaign stored rootkit DLLs, driver paths, and AES keys under these keys to configure its stealthy user-mode rootkit.

Related detections9 linkedT1112 — drag to rearrange
Suspicious Fake ACPIx86 Driver File Creation (via file_event)
Suspicious Disabling of Chromium App-Bound Encryption via Policy Registry Key (via registry_set)
Malicious ld.so.preload Hijack Loading libcext by Auto-Color (via process_creation)
Windows reg.exe Registry Tampering of Internal Tool and Explorer Policy Settings (T1112)
Suspicious Disabling of Restricted Admin Mode via Registry (via registry_set)
Suspicious Loading of Malicious Netfilter Kernel Module for Traffic Signaling
Malicious Kernel Driver Load from User AppData Directory
Malicious WDigest UseLogonCredential Enabled for Cleartext Credential Theft (via registry_set)
Suspicious ClickFix RunMRU Entry Recording LOLBIN Command from Run Dialog
Suspicious Rootkit Configuration Registry Keys (via registry_set)
Pivot detection · T1112 · 9 related

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