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

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. 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.

Related detections9 linkedT1218 — drag to rearrange
Suspicious .NET LOLBin Execution via CasPol or RegAsm
Possible DarkGate DLL Sideloading via iTunesHelper Loading CoreFoundation
Suspicious extrac32 CAB Extraction Abuse
Malicious cdb.exe Masquerading as fontdrvhost in ProgramData (via process_creation)
Malicious certutil Decodehex Payload Reconstruction by DarkGate
Malicious MSIX Package Execution via App Installer ms-appinstaller Protocol (via process_creation)
Malicious ViPNet Backdoor Loader via lumpdiag.exe Path Substitution
Suspicious BitLockerToGo Execution from Unusual Parent
Suspicious Proxy Execution via pcalua
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.