huntrule

Windows Security 4697: Obfuscated PowerShell via use of Clip.exe from scripts

Alerts on EID 4697 service installations where the service file name matches Clip/clipboard indicators tied to obfuscated PowerShell.

FreeReviewedSigma · High · v2
Product
windows
Service
security
Author
Nikita Nazarov, oscd.community (SigmaHQ), DRL 1.1
Published
2020-10-09
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Execution → Defense Evasion

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags Windows Security event 4697 when a service is installed using a service file name that contains Clipboard- or related Clip.exe indicators. Attackers may use Clip.exe from scripts to quickly stage or move content while obscuring PowerShell execution and intent. It relies on System Security Extension logging of service-install events (EventID 4697) and matches on the recorded service file name string.

Reporting behind it

Related detections9 linkedT1027 — drag to rearrange
Suspicious PowerShell Invoke-Expression with Replace Obfuscation
Malicious Emmenhtal JavaScript Loader Spawning Encoded PowerShell
Suspicious Python Interpreter Launching Encoded PowerShell via subprocess
Suspicious PS1Bot PowerShell Payload Written to ProgramData (via file_event)
Malicious Non-Interactive Encoded PowerShell Stager (via process_creation)
Suspicious Hidden PowerShell Executing Substring of Dropped File
PowerShell Encoded or Download-Cradle Command Line (via process_creation)
Obfuscated Encoded PowerShell Payload Deployed - PowerShell (via powershell)
Suspicious PowerShell AES Decryption and Reflective Method Invocation in SolarMarker
Windows Security 4697: Obfuscated PowerShell via use of Clip.exe from scripts
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.