Windows: Malicious Child Process Execution via vsjitdebugger.exe Just-In-Time Debugger

Flags unusual executables launched by vsjitdebugger.exe on Windows, excluding common Visual Studio helper/debugger children.

FreeReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
Agro (@agro_sev), Ensar Şamil (@sblmsrsn), oscd.community (SigmaHQ), DRL 1.1
Published
2020-10-14
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 identifies process creation where the parent process is Microsoft Visual Studio Just-In-Time Debugger (vsjitdebugger.exe), but excludes likely benign helper/debugger scenarios. Attackers can abuse this functionality to launch and run arbitrary executables under the context of a trusted, developer-installed component. It relies on process creation telemetry capturing both the parent image path and the spawned child image path on Windows.

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: Malicious Child Process Execution via vsjitdebugger.exe Just-In-Time Debugger
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.