Suspicious Chafer Backdoor Registry Configuration under Microsoft DRM Key

PremiumReviewedSigma · Medium · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-08-16
Updated
2026-08-28

ATT&CK techniques

Persistence → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects creation or modification of a Log value under the Microsoft DRM registry key which the Chafer backdoor uses as an execution gate and configuration store. Observed in NCC Group research analyzing the Chafer backdoor. Abuse of the DRM key as a covert configuration location is an uncommon behavior worth surfacing.

Related detections9 linkedT1112 — drag to rearrange
Windows reg.exe Registry Tampering of Internal Tool and Explorer Policy Settings (T1112)
Suspicious Disabling of Restricted Admin Mode via Registry (via registry_set)
Malicious WDigest UseLogonCredential Enabled for Cleartext Credential Theft (via registry_set)
Suspicious ClickFix RunMRU Entry Recording LOLBIN Command from Run Dialog
Suspicious Access to Chrome Encrypted Preference MAC Registry Values (via registry_set)
Suspicious Flax Typhoon Network Level Authentication Disabled via Registry (via registry_set)
Suspicious Deletion of Terminal Server Client History via reg by UNC1549
Suspicious Registry Class Key Creation for COLDRIVER Persistence
Suspicious Modification of CloudFiles BlockedApps Policy via registry_set
Suspicious Chafer Backdoor Registry Configuration under Microsoft DRM Key
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.