huntrule

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
AnalysisDetection

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. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

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

Reporting behind it

Related detections9 linkedT1021.002 — drag to rearrange
Malicious NetExec SMB Enumeration Execution (via process_creation)
Malicious WMIexec Style Command Output Redirection to Local Admin Share
Malicious Cobalt Strike Default Named Pipe Activity
Suspicious PsExec Service Launching Encoded PowerShell Payload
Suspicious Impacket Style Command Execution with ADMIN Share Output Redirect
Suspicious Active Directory Reconnaissance via In-Memory Offensive PowerShell (via ps_script)
Suspicious NetExec Post-Exploitation Tool Execution via nxc (via process_creation)
Suspicious SMB Admin Share Mapping for Lateral Tool Transfer (via process_creation)
Suspicious Impacket Remote Execution Tool Usage via process_creation
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.