Malicious Tusk Persistence via FJ_load Scheduled Task

PremiumReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-10-07
Updated
2026-10-07

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 creation of a scheduled task named FJ_load that runs madHcCtrl.exe at user logon, the persistence mechanism of the Tusk infostealer campaign. The task keeps the loader resident across reboots, so detecting its creation catches the campaign at the persistence stage.

Related detections9 linkedT1053.005 — drag to rearrange
Malicious EastWind Persistence via schtasks DRMserver Task
Possible SocGholish Update Task Running Batch File at Highest Privileges (via process_creation)
Suspicious Scheduled Task Creation in Public Writable Directory via schtasks (via process_creation)
Suspicious Scheduled Task Executing Payload from AppData
Suspicious Scheduled Task Creation With RMMProject Loader Task Names
Malicious Scheduled Task Running svchost32 Proxy from Windows Temp
Suspicious Scheduled Task Recovery Diagnostics Running PowerShell Script via process_creation
Suspicious Scheduled Task Application Maintenance Executing Core Payload
Malicious Scheduled Task Executing Binary from NETLOGON
Malicious Tusk Persistence via FJ_load Scheduled Task
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.