Suspicious Executable Run from IIS aspnet_client or Windows Tasks Directory via process_creation

PremiumReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-09-24
Updated
2026-09-24

ATT&CK techniques

Initial Access
  1. Recon

  2. Resource Dev

  3. Execution

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects process execution from the IIS inetpub aspnet_client folder or the Windows Tasks directory, staging locations abused by Ballistic Bobcat after exploiting internet-facing servers to deploy the Sponsor backdoor. Binaries running from these web-writable or system-hidden paths strongly indicate post-exploitation persistence.

Related detections9 linkedT1190 — drag to rearrange
Suspicious Telerik UI RadAsyncUpload Request Indicating CVE-2019-18935 Exploitation (via webserver)
Malicious IIS Worker Process Spawning Shell for Out-of-Band Interaction via Command Line
Malicious wp2shell WordPress Exploitation via Batch Endpoint User Agent
Suspicious TOLLBOOTH Webshell URI Access
Suspicious ffuf Fuzzing Requests Against Web Server
Suspicious AI Agent Compromise via Web Worker Spawning Shell or Network Tool
Malicious wp2shell WordPress RCE via Web Server Spawning Shell Recon
Suspicious Child Process Spawned by IIS Worker Process w3wp
Possible Log4Shell Exploitation via Java Spawning Shell or Download Utility
Suspicious Executable Run from IIS aspnet_client or Windows Tasks Directory via process_creation
Pivot detection · T1190 · 9 related

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