Suspicious Code Compilation via Aspnet_compiler LOLBIN (via process_creation)

PremiumReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-09-04
Updated
2026-09-04

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 detects aspnet_compiler.exe being executed to compile and run arbitrary code, a signed-binary proxy technique used by AsyncRAT and similar tooling to build a payload in place while evading application allowlisting. Aspnet_compiler abuse is a defense-evasion technique in the Red Canary Threat Detection Report. Detecting this rarely-interactive binary surfaces trusted-utility code execution.

Related detections9 linkedT1127 — drag to rearrange
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 involving VSIISExeLauncher.exe with -p and -a arguments
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
Suspicious Code Compilation via Aspnet_compiler LOLBIN (via process_creation)
Pivot detection · T1127 · 9 related

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