huntrule

Windows Provisioning Registry Key Abuse Leading to Indirect Execution via Provlaunch.exe

Flags Windows command lines referencing the provisioning commands registry path commonly abused for Provlaunch.exe-based indirect execution.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Nasreddine Bencherchali (Nextron Systems), Swachchhanda Shrawan Poudel (SigmaHQ), DRL 1.1
Published
2023-08-08
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 process creation events where the command line contains the provisioning commands registry path 'SOFTWARE\Microsoft\Provisioning\Commands\'. Abuse of this location can enable indirect command execution through Provlaunch.exe, helping attackers run additional payloads while blending into legitimate provisioning-related activity. It relies on Windows process creation telemetry with access to the full command line string.

Reporting behind it

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 Provisioning Registry Key Abuse Leading to Indirect Execution via Provlaunch.exe
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.