Malicious PowerShell Runtime Loaded Outside PowerShell Host

PremiumReviewedSigma · High · v1
Product
windows
Category
image_load
Author
HuntRule
Published
2026-10-02
Updated
2026-10-02

ATT&CK techniques

Execution → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects the System.Management.Automation.dll PowerShell runtime being loaded by a process other than a legitimate PowerShell host, the unmanaged PowerShell technique used by Cobalt Strike to execute PowerShell in memory without spawning powershell.exe. Running PowerShell inside an arbitrary process evades monitoring that watches the PowerShell binary. A non-host process loading the automation assembly is a strong injection indicator.

Related detections9 linkedT1059.001 — drag to rearrange
In-Memory Phantom Stealer In-Memory Process Injection via PowerShell Add-Type API Chain (via ps_script)
Suspicious word_update.exe Spawning Command Shell in Remcos Chain (via process_creation)
Suspicious PowerShell Shellcode Loader via Function Pointer Delegate
Suspicious AutoIt Interpreter Launched by Script Host or Shell
Windows PowerShell Base64-encoded shellcode in ScriptBlockText
Malicious Fickle Stealer Remote PowerShell Execution From UNC Share (via process_creation)
Suspicious PDF Editor Updater Binary Spawning PowerShell (via process_creation)
PowerShell ExecutionPolicy Set to Bypass via Registry (via registry_set)
Malicious XWorm Script Chain Execution from ProgramData Music Visuals Directory (via process_creation)
Malicious PowerShell Runtime Loaded Outside PowerShell Host
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.