Malicious Windows Service Installation Executing a Script Interpreter (via process_creation)

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

ATT&CK techniques

Execution → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Defense Evasion

  5. Cred Access

  6. Discovery

  7. Lateral Movement

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule detects creation of a Windows service via sc.exe whose binary path points at a command shell, PowerShell or another script interpreter instead of a normal service executable. Service Execution is a top technique in the Red Canary Threat Detection Report, used by adversaries and tools like PsExec to run code as SYSTEM and to persist. Flagging service installs that launch interpreters catches both privilege escalation and persistence at setup time.

Related detections9 linkedT1543.003 — drag to rearrange
Windows System Service Installation of Remote Access Tool Services (Event 7045/7036)
Windows Security Event 4697 Service Install of Remote Access Tools
Windows Service Control Manager detects Sliver C2 default service installations via service creation events
Windows Registry Service Install Indicators for Cobalt Strike Staging
Windows Service Control Manager: ProcessHacker service runs as LocalSystem
Windows Service Control Manager Events: Suspicious Service Install Paths used by Cobalt Strike
Windows Security 4697 Alerts for Service Installations Using Cobalt Strike Beacon Payloads
Windows Service Creation: ServiceName javamtsup (Event ID 4697)
SwimSnake Kernel Driver Service Creation from Public Directory via sc.exe (via process_creation)
Malicious Windows Service Installation Executing a Script Interpreter (via process_creation)
Pivot detection · T1543.003 · 9 related

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