huntrule

Windows reg.exe Changes Desktop Background Policy Values

Alerts when reg.exe is used to modify Windows registry settings that control wallpaper or desktop background behavior.

FreeReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
Stephen Lincoln @slincoln-aiq (AttackIQ) (SigmaHQ), DRL 1.1
Published
2023-12-21
Updated
2026-07-30
AnalysisDetection

ATT&CK techniques

Persistence → Impact

  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 process executions of reg.exe with command lines containing registry modifications related to desktop background and wallpaper settings. Attackers can use these changes to disrupt user visibility or influence what the user sees on the desktop, such as displaying ransom-style imagery or impairing normal use. It relies on Windows process creation telemetry, matching reg.exe invocation with specific registry key paths and policy/value parameters.

Reporting behind it

Related detections9 linkedT1112 — drag to rearrange
Windows Registry Change to Desktop Wallpaper Policy or Settings
Malicious Enabling of Restricted Admin Mode via Registry by UAT-8837
Suspicious Enabling of Remote Desktop via fDenyTSConnections Registry by DeadLock Ransomware
Malicious Service DLL Hijack for Persistence via Lotus Blossom
Suspicious Loopback Proxy Server Configured via Registry (via registry_set)
Malicious WDigest Credential Caching Enabled via Registry (via registry_set)
Suspicious Remote Desktop Enabled via fDenyTSConnections Registry by Sandworm
Malicious Gh0stBins RAT Registry Marker HHClient
Suspicious PebbleDash C2 Configuration Stored Under WMI Security Key (via registry_set)
Windows reg.exe Changes Desktop Background Policy Values
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.