Windows Service Control Manager: HackTool Service Installation or Start via Suspicious Service Names

Detects Windows service creation/start events tied to hacktool-like service names or ImagePath indicators.

FreeReviewedSigma · High · v2
Product
windows
Service
system
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-03-21
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 Windows service creation and subsequent service state changes by the Service Control Manager when the service name matches known credential-dumping or bypass-related strings. Attackers often register services to run malicious code as a background process with elevated privileges, helping them persist or execute tooling. It relies on Windows System service telemetry, specifically events tied to Service Control Manager activity (7045 and 7036) and matching service name substrings and an ImagePath indicator containing 'bypass'.

Related detections9 linkedT1569.002 — drag to rearrange
PsExec Remote Service Execution on Target Host (via process_creation)
Renamed Procdump Tool Used for Dumping LSASS Process (via process_creation)
Suspicious Service Installation Masquerading as winupd
Suspicious PSexec Application Execution (via process_creation)
Malicious Metasploit PsExec Named Pipe Command Execution
Malicious PsExec Service Installation via PSEXESVC
Malicious NotPetya Payload Execution via Rundll32 Ordinal Export from Windows Directory
Suspicious Lateral Movement via PsExec Service (via process_creation)
Possible PsExec Remote Service Installation with Randomly Named Service (via security)
Windows Service Control Manager: HackTool Service Installation or Start via Suspicious Service Names
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.