Windows Devtoolslauncher.exe LaunchForDeploy Executes a Specified Binary

Alerts when devtoolslauncher.exe runs with LaunchForDeploy, indicating it may launch another binary on Windows.

FreeReviewedSigma · High · v2
Product
windows
Category
process_creation
Author
Beyu Denis, oscd.community (rule), @_felamos (idea) (SigmaHQ), DRL 1.1
Published
2019-10-12
Updated
2026-07-31

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 process creation events where Devtoolslauncher.exe is launched with a command line containing 'LaunchForDeploy'. It can indicate an attacker using a signed Microsoft Windows binary to execute another program, supporting defense-evasion and stealthy execution. The detection relies on Windows process creation telemetry capturing the image path and the full command line.

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 Devtoolslauncher.exe LaunchForDeploy Executes a Specified Binary
Pivot detection · T1218 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

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