Windows System Service Control: Obfuscated cmd Launching clip.exe for PowerShell

Flags service creation (Event 7045) with obfuscated cmd ImagePath using clip.exe/clipboard PowerShell execution patterns.

FreeReviewedSigma · High · v2
Product
windows
Service
system
Author
Jonathan Cheong, oscd.community (SigmaHQ), DRL 1.1
Published
2020-10-13
Updated
2026-07-31

ATT&CK techniques

Execution → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

Identifies Windows Service Control Manager events where the service ImagePath contains command execution patterns including cmd, an inline command separator (&&), and PowerShell clipboard access (clipboard]::), consistent with obfuscated invocation via clip.exe. Attackers may use this approach to conceal PowerShell payload execution and stage commands through built-in utilities. The detection relies on System channel telemetry capturing Service Control Manager event 7045 and matching the ImagePath string for these specific obfuscation indicators.

Related detections9 linkedT1027 — drag to rearrange
Malicious FIN7 Powertrash Loader Execution via Obfuscated PowerShell (via process_creation)
Suspicious XOR Obfuscated PowerShell from ClickFix Distribution
Suspicious PowerShell Executing Code from Environment Variable (via process_creation)
Suspicious In-Memory Runspace Execution via PowerShell Script Block
Suspicious Encoded PowerShell Using Base64 Stream Decompression Routines (via process_creation)
Suspicious PowerShell In-Memory Execution with AES Decryption
Suspicious Encoded PowerShell Command Execution
Suspicious PEAKLIGHT Memory-Only PowerShell Downloader Flags (via process_creation)
Obfuscated PowerShell Script: Indirect Cmdlet Execution via ExportedCommands Array Index
Windows System Service Control: Obfuscated cmd Launching clip.exe for PowerShell
Pivot detection · T1027 · 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.