Windows: Alert on Suspicious Child Processes Spawned by provlaunch.exe

Detects provlaunch.exe launching suspicious child executables and processes from common temp/task paths on Windows.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2023-08-08
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 when provlaunch.exe spawns specific child processes commonly abused for execution and scripting, including calc.exe, cmd.exe, cscript.exe, mshta.exe, notepad.exe, powershell.exe/pwsh.exe, regsvr32.exe, rundll32.exe, and wscript.exe. It also catches cases where the spawned process command path includes typical staging or task locations such as PerfLogs, Temp, Users\Public, AppData\Temp, and Windows\Tasks/Temp. This matters because attackers may use provlaunch.exe to proxy execution and move into more capable tooling or script interpreters, which is observable via process creation telemetry on Windows.

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: Alert on Suspicious Child Processes Spawned by 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.