Windows: Detect sc.exe Service Config binPath Changes to Suspicious Commands/Paths

Alerts when sc.exe updates a service binPath to point at suspicious commands or commonly abused directories.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Victor Sergeev, oscd.community, Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2019-10-21
Updated
2026-07-30

ATT&CK techniques

Persistence → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule flags Windows process creation events where sc.exe is used to modify a service configuration containing both "config" and "binPath", with the command line referencing a suspicious script execution tool or executable path. Service path changes matter because they can redirect how a service runs on startup, enabling persistence or privilege escalation. It relies on process creation telemetry capturing the image path (sc.exe) and the full command line text.

Related detections9 linkedT1543.003 — drag to rearrange
Malicious Service DLL Hijack for Persistence via Lotus Blossom
Malicious TinyTurla ServiceDll Registration via svchost Group (via registry_set)
Suspicious ToyMaker LAGTOY Service Creation Masquerading as WmiPrvSV via sc.exe
Malicious Service Creation With Autostart binPath via sc.exe (via process_creation)
Malicious svchost Service Creation for TinyTurla Persistence (via process_creation)
Malicious Service Creation Masquerading as nslookup (via process_creation)
Interactive Service Creation Executing cmd via sc.exe
Malicious Known Vulnerable Driver Load for BYOVD Attack
Malicious ValleyRAT KernelQuick Rootkit Service and Shellcode Store Registry Keys
Windows: Detect sc.exe Service Config binPath Changes to Suspicious Commands/Paths
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.