Malicious PPL Abuse via ClipUp Protected Process Launch

PremiumReviewedSigma · High · v1
Category
process_creation
Author
HuntRule
Published
2026-08-25
Updated
2026-08-28

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 detects the ClipUp.exe utility launched with a protected process light argument, the technique RONINGLOADER uses to spawn a signed binary as a PPL and disable Microsoft Defender. Abusing ClipUp to obtain a protected process lets the loader tamper with security services that normally block it.

Related detections9 linkedT1685 — drag to rearrange
Malicious Microsoft Defender Real-Time Monitoring Disabled via Set-MpPreference (via process_creation)
Suspicious Windows Defender Exclusion Added via PowerShell via Process Creation (via process_creation)
Suspicious DLL Sideload of profiler16.dll (via image_load)
Malicious PUBLOAD Fake Windows Update C2 Request via Proxy (via proxy)
Malicious TCC AppleEvents Reset via Tccutil
Suspicious MicrosoftEdgeUpdate Launched with Dat Config File
Suspicious GoogleUpdate Binary Executing From Non-Standard Path (via process_creation)
Suspicious ESXi Management Agent Stop via vpxa init Script (via process_creation)
Malicious ESXi Firewall Disable via esxcli (via process_creation)
Malicious PPL Abuse via ClipUp Protected Process Launch
Pivot detection · T1685 · 9 related

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