Windows Scheduled Task Creation via schtasks.exe Using sshd/ssh.exe for Tunnel Setup

Alerts when schtasks.exe creates scheduled tasks that invoke sshd.exe or ssh.exe with tunnel-related arguments.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Rory Duncan (SigmaHQ), DRL 1.1
Published
2025-07-14
Updated
2026-07-30

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 flags process executions of schtasks.exe where the command line includes a scheduled task creation (/create) that references sshd.exe with -f or ssh.exe with -i. Such behavior can indicate an attacker setting up persistent access by periodically launching an SSH-based tunnel or service. The detection relies on Windows process creation telemetry capturing the Image/OriginalFileName and full command line arguments used to create the task.

Related detections9 linkedT1053.005 — drag to rearrange
Suspicious Scheduled Task CacheTask Reconfigured to Run as SYSTEM
Malicious NodeSnake RAT Persistence via Scheduled Task and Node.js (via process_creation)
Malicious Scheduled Task Masquerading as Windows Defender Sync via schtasks (via process_creation)
Suspicious Scheduled Task Creation Launching mshta via schtasks (via process_creation)
Suspicious Service or Task Named windowsinspectionupdate (via process_creation)
Suspicious Scheduled Task Creation Referencing dllFake Batch Scripts (via process_creation)
Suspicious Scheduled Task Creation With WebDAV Loader Task Names (via process_creation)
Suspicious Scheduled Task Creation with ClickFix Update Recon Name (via process_creation)
Malicious Scheduled Task Named Gentlemen via Schtasks
Windows Scheduled Task Creation via schtasks.exe Using sshd/ssh.exe for Tunnel Setup
Pivot detection · T1053.005 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.