Non-privileged reg.exe or PowerShell registry service configuration changes on Windows

Flags non-admin reg.exe or PowerShell activity targeting service registry configuration paths on Windows.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Teymur Kheirkhabarov (idea), Ryan Plas (rule), oscd.community (SigmaHQ), DRL 1.1
Published
2020-10-05
Updated
2026-07-30

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 identifies process executions by non-privileged users running reg.exe or PowerShell commands that include service-related registry paths. It matters because modifying service configuration can enable persistence or interfere with defenses without needing elevated privileges. The detection relies on Windows process creation telemetry, including command line content and integrity level indicators (Medium or S-1-16-8192).

Related detections9 linkedT1112 — drag to rearrange
Suspicious Registry Value under Console WindowsUpdates for C2 Storage
Suspicious Office VBA Object Model Access Enabled via Registry (via registry_set)
Suspicious PowerShell Payload Staging in HKCU Printers Registry Key
Suspicious Rootkit Configuration Registry Keys (via registry_set)
Suspicious Disabling of Chromium App-Bound Encryption via Policy Registry Key (via registry_set)
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
Non-privileged reg.exe or PowerShell registry service configuration changes on Windows
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.