huntrule

Windows Registry Key Abuse via Provisioning Commands for Proxy Binary Execution

Flags registry modifications to the Provisioning Commands key path that may enable indirect execution via Provlaunch.exe.

FreeReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
Swachchhanda Shrawan Poudel (SigmaHQ), DRL 1.1
Published
2023-08-02
Updated
2026-07-30
AnalysisDetection

ATT&CK techniques

Defense Evasion

  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 registry activity involving the Provisioning Commands path under \\SOFTWARE\\Microsoft\\Provisioning\\Commands\\. Attackers can misuse this area to redirect execution through a proxy-style binary such as Provlaunch.exe, helping them run code indirectly while blending into legitimate provisioning mechanisms. The detection relies on registry-set telemetry that includes the TargetObject field containing the monitored registry path.

Reporting behind it

Related detections9 linkedT1218 — drag to rearrange
Suspicious Cabinet Extraction of Masqueraded vstm Archive via extrac32
Malicious DLL Execution via Wuauclt Update Handler (via process_creation)
Malicious aspnet_compiler.exe Injection Host Spawned by PowerShell via process_creation
Malicious regsvcs LOLBin Loading Ransomware DLL from UNC Path
Suspicious RegAsm or RegSvcs Spawned by Script Host (via process_creation)
Suspicious Extexport DLL Side-Loading Execution
Malicious ClickFix Execution Chain Spawning MSHTA via Pcalua on EtherRAT Infection
Suspicious TALONITE Certutil LOLBIN Decode and Download Abuse (via process_creation)
Suspicious Renamed git Binary gcmd.exe Execution (via process_creation)
Windows Registry Key Abuse via Provisioning Commands for Proxy Binary Execution
Pivot detection · T1218 · 9 related

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