Suspicious Indirect PowerShell Execution via Forfiles LOLBIN (via process_creation)

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

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects the forfiles utility being used to indirectly launch cmd or PowerShell, an execution-proxy technique observed in the STRT LNK phishing analysis to break the normal parent-child chain and evade detection. Adversaries leverage forfiles as an intermediary so the spawned shell does not descend directly from the malicious shortcut, so this behavior warrants review in phishing-triage context.

Related detections9 linkedT1202 — drag to rearrange
Uncommon Child Process Spawned by XBootMgrSleep.exe (Windows Performance Toolkit)
Windows SFTP.exe Indirect Command Execution via ProxyCommand
WSL Process Execution of Kali Linux on Windows
Windows vshadow.exe Proxy Execution via -exec Script/Command
Windows ConHost Spawning Suspicious Script and Command-Line Child Processes
Windows Execution of Renamed NirCmd.exe (nircmd.exe/nircmdc.exe) via PE OriginalFileName
Windows: Detect renamed PingCastle binary execution via PE metadata and scanner command-line
Windows Process Creation: Execution of Renamed curl.exe via PE Metadata
Suspicious Child Process Creation from BgInfo.EXE on Windows
Suspicious Indirect PowerShell Execution via Forfiles LOLBIN (via process_creation)
Pivot detection · T1202 · 9 related

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