Suspicious schtasks Persistence Spawned from PowerShell or Script Chain

PremiumReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-05-19
Updated
2026-08-28

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 detects schtasks creating a scheduled task when launched from a PowerShell or command-shell parent, a persistence step observed in the Suky Castle ClickFix-style campaign where an obfuscated PowerShell to cmd to attrib to schtasks chain established persistence. It captures scheduled-task creation originating from an interactive scripting context rather than an installer. Detecting this is important because attacker-driven schtasks activity typically descends from a script host rather than a legitimate management tool.

Related detections9 linkedT1053.005 — drag to rearrange
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
Malicious Scheduled Task Masquerading as Defender NisSrv via Schtasks
Malicious Scheduled Task Masquerading as Windows Defender Updater (via process_creation)
Suspicious Scheduled Task Masquerading as Palo Alto Cortex Services
Malicious Scheduled Task Running rundll32 w32analytics (via process_creation)
Malicious Scheduled rundll32 Execution of ProgramData VMware DLL by BianLian
Suspicious schtasks Persistence Spawned from PowerShell or Script Chain
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.