Windows Service Control Manager flags smbexec.py-style service installation via suspicious ImagePath

Flags suspicious Windows service installations matching a specific service name and BAT/delete command patterns in Event 7045.

FreeReviewedSigma · High · v2
Product
windows
Service
system
Author
Omer Faruk Celik (SigmaHQ), DRL 1.1
Published
2018-03-20
Updated
2026-07-31

ATT&CK techniques

Execution → Lateral Movement
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule catches Windows service creation events (EventID 7045) where the Service Control Manager reports a specific service name and ImagePath patterns consistent with smbexec.py-style execution chains. Attackers can leverage this technique to run remote code via a temporary or misleading Windows service, blending execution into normal service installation telemetry. It relies on Windows System logs capturing Service Control Manager provider events, including Provider_Name, EventID, ServiceName, and ImagePath contents.

Related detections9 linkedT1021.002 — drag to rearrange
Malicious PsExec Service Installation via PSEXESVC
Suspicious Lateral Movement via PsExec Service (via process_creation)
Possible PsExec Remote Service Installation with Randomly Named Service (via security)
Windows Named Pipe Creation: Default RemCom Pipe Name
Windows Named Pipe Created for CSExec Default Pipe Name
Windows Registry Service Install Indicators for Cobalt Strike Staging
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 rundll32.exe execution with no parameters or arguments
Windows Service Control Manager flags smbexec.py-style service installation via suspicious ImagePath
Pivot detection · T1021.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.