Windows Service Control Manager Detects CSExecSvc Installation and Execution

Flags Windows service creation for csexecsvc with image path ending in \csexecsvc.exe via Service Control Manager (7045).

FreeReviewedSigma · Medium · v2
Product
windows
Service
system
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2023-08-07
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 identifies attempts to install the CSExec Windows service by matching Service Control Manager events where the service name is csexecsvc and the ImagePath ends with \csexecsvc.exe. Service installation followed by execution is a common method for attackers to gain persistent or remote execution capabilities. It relies on Windows System telemetry from Event ID 7045, including Provider_Name, ServiceName, and ImagePath fields.

Related detections9 linkedT1569.002 — drag to rearrange
Suspicious Executable Launched from Public Music Staging Directory (via process_creation)
Malicious Service Execution via PAExec
Suspicious RemCom Service Named Pipe for Lateral Movement (via pipe_created)
Malicious CACTUS Ransomware Deployment via TotalExec Script (via ps_script)
Malicious PsExec Service Binary Execution from Windows Directory via services.exe (via process_creation)
Malicious Remote Command Execution via smbexec Output Redirection Pattern
Malicious Lateral Movement via PsExec File-List Target
Malicious PsExec SYSTEM Interactive Shell Execution (via process_creation)
Suspicious PsExec Service Named Sliver
Windows Service Control Manager Detects CSExecSvc Installation and Execution
Pivot detection · T1569.002 · 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.