Windows sc.exe Service StartupType Change to Disabled or Demand

Flags sc.exe commands that change a Windows service startup type to disabled or demand.

FreeReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-08-01
Updated
2026-07-30

ATT&CK techniques

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule identifies cases where sc.exe is used with “config” and “start” to set a Windows service startup type to either “disabled” or “demand.” Attackers can use service configuration changes to impair defenses or disrupt recovery by preventing services from starting as expected. The detection relies on Windows process creation telemetry, matching the sc.exe process image/original filename and specific command-line arguments indicating the startup type change.

Related detections9 linkedT1685 — drag to rearrange
Malicious Unsigned VIB Installation on ESXi Host via esxcli (via process_creation)
Suspicious In-Memory PowerShell Execution from Web Server via Automation Assembly (via image_load)
Malicious EDR Evasion Driver Load from AnyDesk Directory via k.sys (via image_load)
Malicious Zemana Vulnerable Driver Load for EDR Termination (via image_load)
Suspicious EDRKillShifter Vulnerable Driver Load from User Temp Directory (via image_load)
Malicious AuKill EDR Killer Kernel Driver Load via Process Explorer Driver (via image_load)
Malicious FIN7 AvNeutralizer EDR Killer Execution via Masqueraded Binary (via process_creation)
Suspicious Process Explorer Kernel Driver Dropped as PED.sys via File Creation (via file_event)
Malicious Windows Defender Tampering via Set-MpPreference and Add-MpPreference (via ps_script)
Windows sc.exe Service StartupType Change to Disabled or Demand
Pivot detection · T1685 · 9 related

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