Windows: Process creation involving VSIISExeLauncher.exe with -p and -a arguments

Flags Windows launches of VSIISExeLauncher.exe with "-p" and "-a" parameters, consistent with potential arbitrary binary execution.

FreeReviewedSigma · Medium · v2
Product
windows
Category
process_creation
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-06-09
Updated
2026-07-31

ATT&CK techniques

Execution → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule flags Windows process executions where VSIISExeLauncher.exe is launched and the command line contains both " -p " and " -a ", indicating it was used with parameters that can drive execution of attacker-controlled payloads. Attackers may leverage this signed Microsoft-associated binary to blend in with legitimate development tooling and reduce detection confidence. The detection relies on process creation telemetry, matching the executable name and the presence of specific argument patterns in the command line.

Related detections9 linkedT1127 — drag to rearrange
Suspicious Code Compilation via Aspnet_compiler LOLBIN (via process_creation)
ArcSOC.exe Creates Suspicious Script/Executable Files on Windows
Suspicious Child Process of aspnet_compiler.exe on Windows
Suspicious aspnet_compiler.exe Execution from User or Temp Paths on Windows
Windows: Detect kavremover-related LOLBIN command-line usage
Windows node.exe Execution with -e/--eval and suspicious child process usage
Windows Process Creation: Mftrace.exe Child Process Execution
Windows Process Creation: Remote.exe Execution
Windows Process Creation: wfc.exe Execution for Workflow Command-line Compiler Abuse
Windows: Process creation involving VSIISExeLauncher.exe with -p and -a arguments
Pivot detection · T1127 · 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.