Windows: Suspicious Script/Command Child Processes Spawned by ArcSOC.exe

Alerts when ArcSOC.exe launches cmd/cscript/mshta/powershell/wscript and similar interpreters, indicating potential remote code execution.

FreeReviewedSigma · High · v2
Product
windows
Category
process_creation
Author
Micah Babinski (SigmaHQ), DRL 1.1
Published
2025-11-25
Updated
2026-07-31

ATT&CK techniques

Execution
  1. Recon

  2. Resource Dev

  3. Initial Access

  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 flags process creation events where ArcSOC.exe spawns common script interpreters and command-line tooling such as cmd.exe, PowerShell, and WScript/WSH binaries. Such parent-child relationships can indicate remote code execution attempts launched from the ArcGIS Server REST service host process. It relies on Windows process creation telemetry with the parent image ending in \ArcSOC.exe and the child image matching known interpreter/tool executable names.

Related detections9 linkedT1059 — drag to rearrange
Linux: Shell spawned by rsync without -e flag in command line
Suspicious Child Processes Spawned by Browsers on macOS
Suspicious Python Execution via Renamed Synaptics Binary
MSBuild Executing Non-Project File or Remote Payload
Possible Ivanti Pulse Connect Secure Command Injection via License Keys-Status Endpoint (via webserver)
Possible Craft CMS RCE via Query-String CLI Option Injection
Possible Aspera Faspex Pre-Auth RCE via YAML Deserialization in package_relay (via webserver)
Possible Sitecore Pre-Auth RCE via Report.ashx Insecure Deserialization (via webserver)
Possible WatchGuard Pre-Auth RCE via agent login XML-RPC CVE-2022-26318
Windows: Suspicious Script/Command Child Processes Spawned by ArcSOC.exe
Pivot detection · T1059 · 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.