Windows: WinSCP Execution from Non-Standard Directory

Flags WinSCP started from a non-default directory on Windows to surface potential portable execution.

FreeReviewedSigma · Medium · v5
Product
windows
Category
process_creation
Author
frack113 (SigmaHQ), DRL 1.1
Published
2025-10-12
Updated
2026-07-31

ATT&CK techniques

Exfiltration
  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. Impact

What it detects

Identifies process creation where the executed binary is WinSCP (WinSCP.exe / OriginalFileName winscp.exe) from a directory other than C:\Program Files (x86)\WinSCP\. Attackers may use portable copies or unusual staging locations to blend in while leveraging legitimate tooling. This relies on Windows process creation telemetry, including Image path and OriginalFileName, to compare execution location against the expected installation directory.

Related detections9 linkedT1048 — drag to rearrange
Malicious Bulk Data Exfiltration via Rclone (via process_creation)
BITS Payload Downloaded via Commandline (via process_creation)
BITS Payload Downloaded via PowerShell (via powershell)
Data Exfiltration to WebDAV Share via curl Upload
Suspicious Data Exfiltration via Finger LOLBIN
Malicious Bad Apples Data Exfiltration via snmptrap OID
Suspicious rclone Masquerading as Avast Binary by The Gentlemen RaaS (via process_creation)
Windows DNS Queries to git-tanstack.com and filev2.getsession.org
Windows Process Execution: Restic Backup Tool Command-Line Indicators
Windows: WinSCP Execution from Non-Standard Directory
Pivot detection · T1048 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. 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.