huntrule

Windows: SharpUp (SharpUp.exe) Local Privilege Escalation Tool Execution

Flags SharpUp.exe execution on Windows when command line indicators reference common privilege-escalation targets.

FreeReviewedSigma · Critical · v2
Product
windows
Category
process_creation
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-08-20
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Execution → Discovery

  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 the executable is SharpUp.exe and the command-line and description indicate the SharpUp privilege-escalation checks are being run. Attackers may use SharpUp to discover and abuse misconfigurations such as hijackable paths, unquoted service paths, DLL hijacking, modifiable service binaries, scheduled task abuse, and exposed GPP passwords to gain higher privileges. It relies on Windows process creation telemetry, including the image path, process description, and command-line content.

Reporting behind it

Related detections9 linkedT1569.002 — drag to rearrange
Suspicious Executable Launched from Public Music Staging Directory (via process_creation)
Malicious Service Execution via PAExec
Suspicious RemCom Service Named Pipe for Lateral Movement (via pipe_created)
Malicious CACTUS Ransomware Deployment via TotalExec Script (via ps_script)
Malicious PsExec Service Binary Execution from Windows Directory via services.exe (via process_creation)
Malicious Remote Command Execution via smbexec Output Redirection Pattern
Malicious Lateral Movement via PsExec File-List Target
Malicious PsExec SYSTEM Interactive Shell Execution (via process_creation)
Suspicious PsExec Service Named Sliver
Windows: SharpUp (SharpUp.exe) Local Privilege Escalation Tool Execution
Pivot detection · T1569.002 · 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.