huntrule

Windows Process Creation: SharpSuccessor.exe Execution with Impersonation Parameters

Alerts on SharpSuccessor.exe command-line patterns indicative of Windows privilege escalation attempts.

FreeReviewedSigma · High · v2
Product
windows
Category
process_creation
Author
Swachchhanda Shrawan Poudel (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2025-06-06
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Priv Esc

  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 process creation events where SharpSuccessor.exe is executed with command-line arguments indicating impersonation. An attacker could use this tool to attempt privilege escalation in Active Directory environments by leveraging the impersonation-related options. The detection relies on Windows process telemetry, specifically the executable name/path, original file name, and command-line contents.

Reporting behind it

Related detections9 linkedT1068 — drag to rearrange
Malicious JuicyPotato Privilege Escalation Execution (UAT-7237)
Suspicious Dell ControlVault DLL Load by Unexpected Process (ReVault)
Malicious Known Vulnerable Driver Load for BYOVD Attack
Suspicious Vulnerable ASUS AsIO3.sys Driver Load
Malicious Qilin EDR Killer BYOVD Driver Load
Malicious Looney Tunables Privilege Escalation Exploit by Kinsing (via process_creation)
Malicious Kerberos proxiable/S4U2self Ticket - CVE-2021-42278/42287 (via security)
Malicious Vulnerable Driver HwRwDrv Loaded for BYOVD
Possible CopyFail Root Exploitation via Python Spawning SUID Shell (via process_creation)
Windows Process Creation: SharpSuccessor.exe Execution with Impersonation Parameters
Pivot detection · T1068 · 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.