Windows: SharPersist Execution via Process Image and Scheduled Task/Startup/Registry/Service Command Lines

Detects SharPersist execution on Windows via process name and persistence-related command-line parameters.

FreeReviewedSigma · High · v2
Product
windows
Category
process_creation
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-09-15
Updated
2026-07-31

ATT&CK techniques

Execution → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Defense Evasion

  5. Cred Access

  6. Discovery

  7. Lateral Movement

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule identifies execution of the SharPersist Windows tool by matching the process image name (SharPersist.exe) and specific command-line patterns used to configure persistence. An attacker can leverage SharPersist to deploy multiple persistence mechanisms such as scheduled tasks, startup folder entries, registry run keys, and services. Detection relies on Windows process creation telemetry, including the full image path and command-line arguments.

Related detections9 linkedT1053 — drag to rearrange
Malicious Axios npm Compromise Windows Payload Artifacts wt.exe and 6202033 (via process_creation)
Windows process creation: CrackMapExec execution via characteristic command-line flags
Windows Process Creation: Scheduled Task Creation via schtasks and wscript/vbscript
Windows ATSvc Remote RPC Scheduled Task Creation or Execution (RPC Firewall)
Remote ITaskSchedulerService RPC Create/Execute Scheduled Tasks Used for Lateral Movement
RPC Firewall Alerts for Remote Scheduled Task Creation/Execution via SASec
Windows Suspicious Scheduled Task File Write Targeting System32 Tasks
Windows Registry: New TaskCache entry created by unusual process image
Windows Process Creation: Exchange Server Artifact Discovery and File Staging Patterns
Windows: SharPersist Execution via Process Image and Scheduled Task/Startup/Registry/Service Command Lines
Pivot detection · T1053 · 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.