Malicious aspnet_compiler.exe Injection Host Spawned by PowerShell via process_creation

PremiumReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-08-27
Updated
2026-08-28

ATT&CK techniques

Priv Esc → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects the .NET build utility aspnet_compiler.exe being launched by PowerShell, the process-injection host abused by the multi-stage Phantom Stealer campaign to run reflectively loaded payload code. Spawning the signed compiler from a scripting engine is a wrong-context indicator that the stealer is hollowing a trusted binary to evade detection, exposing the injection before credential theft and SMTP exfiltration.

Related detections9 linkedT1055 — drag to rearrange
Suspicious RegAsm or RegSvcs Spawned by Script Host (via process_creation)
Windows Image Load: coregen.exe Potential DLL Sideloading
Windows: Files created by Microsoft Sync Center (mobsync.exe) with .dll/.exe extensions
Windows Microsoft Sync Center (mobsync.exe) Network Connections to Public IPs
Suspicious AppLaunch.exe Spawned As Injection Target (via process_creation)
Suspicious BugSleep Marker File in Public Directory
Suspicious Cabinet Extraction of Masqueraded vstm Archive via extrac32
Suspicious CRAT Injection Named Pipe ChromeUpdatePipe (via pipe_created)
Malicious DLL Execution via Wuauclt Update Handler (via process_creation)
Malicious aspnet_compiler.exe Injection Host Spawned by PowerShell via process_creation
Pivot detection · T1055 · 9 related

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