Windows SharpMove (.NET) Execution via SharpMove.exe and Action Command-Line Flags

Alerts on SharpMove.exe process execution with command-line actions for DCOM, WMI VBS, and task scheduler.

FreeReviewedSigma · High · v2
Product
windows
Category
process_creation
Author
Luca Di Bartolomeo (CrimpSec) (SigmaHQ), DRL 1.1
Published
2024-01-29
Updated
2026-07-31

ATT&CK techniques

Lateral Movement
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule identifies execution of SharpMove by matching SharpMove.exe in process creation events and requiring command-line activity consistent with the tool’s supported actions. SharpMove can perform multiple post-exploitation tasks, so catching its presence and action flags helps detect attacker-driven execution paths for lateral movement and remote management. The detection relies on Windows process creation telemetry including the executable image name/original file name and command-line parameters.

Related detections9 linkedT1021.002 — drag to rearrange
Suspicious Ransomware Fan-Out Deployment via PsExec Spread (Qilin)
Suspicious Impacket smbexec Command Execution Pattern
Malicious Impacket Wmiexec Remote Command Execution Pattern
Suspicious Remote Admin Share Execution via Conhost
Malicious Network Share Manipulation via Commandline (via process_creation)
Suspicious Number of Oustanding SMB Requests Increased (via process_creation)
Suspicious SMB Insecure Guest Authentication Activated - Native (via security)
Suspicious PSexec Execution Over SMB Share (via security)
Suspicious Permissions Modification on a Network Share (via security)
Windows SharpMove (.NET) Execution via SharpMove.exe and Action Command-Line Flags
Pivot detection · T1021.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.