Suspicious PowerShell Executing Payload From Roaming AppData via Command Line (via process_creation)

PremiumReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-11-01
Updated
2026-11-01

ATT&CK techniques

Execution
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects PowerShell invoked to run an executable located under the Roaming AppData directory, matching the BatLoader chain that launches a dropped payload such as zkoko.exe. It is associated with the BatLoader malware campaign reported by Uptycs. Legitimate installers rarely execute binaries out of the user Roaming profile through PowerShell, so this behavior indicates staged malware execution.

Related detections9 linkedT1059.001 — drag to rearrange
Suspicious PowerShell Spawning mshta for Malware Execution (via process_creation)
Malicious SolarWinds BusinessLayerHost Spawning Suspicious Child Process (SUNBURST) (via process_creation)
Suspicious word_update.exe Spawning Command Shell in Remcos Chain (via process_creation)
Malicious Remote HTA Download and Execution via mshta by UAC-0050 (via process_creation)
Suspicious IIS Worker Process Spawning Command or Scripting Interpreter via SharePoint ToolShell Exploitation (via process_creation)
Suspicious PowerShell Download Cradle Spawned from Explorer via ClickFix Lure (via process_creation)
Malicious Interlock RAT FileFix Download-Cradle via PowerShell WebClient with PowerShell User-Agent (via ps_script)
Malicious Metasploit Stager Delivery via mshta Remote HTA (via process_creation)
Suspicious PowerShell Download of Disguised Payload to ProgramData
Suspicious PowerShell Executing Payload From Roaming AppData via Command Line (via process_creation)
Pivot detection · T1059.001 · 9 related

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