Windows Registry Service Install Indicators for Cobalt Strike Staging

Identifies suspicious Windows service installation registry writes tied to ADMIN$/.exe and %COMSPEC% start powershell patterns.

FreeReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
Wojciech Lesicki (SigmaHQ), DRL 1.1
Published
2021-06-29
Updated
2026-07-30

ATT&CK techniques

Execution → Lateral Movement
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Defense Evasion

  5. Cred Access

  6. Discovery

  7. Collection

  8. C2

  9. Exfiltration

  10. Impact

What it detects

This rule flags registry activity consistent with creating or updating Windows services under the CurrentControlSet/ControlSet service paths. It matches service definitions whose Details contain ADMIN$ and an .exe payload, and whose command string includes %COMSPEC%, start, and powershell. Such patterns matter because service-based execution is a common way for attackers to establish persistence and run commands on remote or lateral systems. The detection relies on Windows registry_set telemetry, specifically the TargetObject and Details fields captured during registry writes.

Related detections9 linkedT1569.002 — drag to rearrange
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
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 System Service Installation of Remote Access Tool Services (Event 7045/7036)
Windows Security Event 4697 Service Install of Remote Access Tools
Windows Registry Service Install Indicators for Cobalt Strike Staging
Pivot detection · T1569.002 · 9 related

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