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

ATT&CK techniques

Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. 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.

Related detections9 linkedT1068 — drag to rearrange
Malicious EDR Evasion Driver Load from AnyDesk Directory via k.sys (via image_load)
Malicious Zemana Vulnerable Driver Load for EDR Termination (via image_load)
Suspicious EDRKillShifter Vulnerable Driver Load from User Temp Directory (via image_load)
Suspicious Process Explorer Kernel Driver Dropped as PED.sys via File Creation (via file_event)
Malicious Payload Download From copy.fail Exploit Host on Linux (via process_creation)
Suspicious su Execution From Uncommon Parent Process on Linux (via process_creation)
Possible noPac sAMAccountName Spoofing via Machine Account Rename
Possible macOS TCC Bypass via mdimport Loading Custom Spotlight Importer
Suspicious CLFS Base Log File Created in SkyPDF ProgramData Path during Zero-Day Exploitation (via file_event)
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.