Windows forfiles.exe Execution with /c Flag Command Proxying

Flags forfiles.exe executions that include the /c flag, indicating potential indirect command execution.

FreeReviewedSigma · Medium · v2
Product
windows
Category
process_creation
Author
Tim Rauch, Elastic, E.M. Anhaus (originally from Atomic Blue Detections, Endgame), oscd.community (SigmaHQ), DRL 1.1
Published
2022-06-14
Updated
2026-07-31

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 matches process creation events where forfiles.exe is launched and its command line includes the /c flag. Attackers can use forfiles to proxy or relay execution of other commands, which may help bypass application control or whitelisting policies. The detection relies on Windows process creation telemetry, specifically the executable image/original filename and the presence of the /c argument in the command line.

Related detections9 linkedT1059 — drag to rearrange
Malicious Web Server Process Spawning Command Interpreter via Web Shell (via process_creation)
Suspicious VMware Guest Operation Output Staging in vmware-system Temp Directory (via file_event)
Malicious Command Shell Spawned by SQL Server via Process Creation (via process_creation)
Suspicious Script Interpreter Spawned by Excel via DarkGate Lure
Suspicious AutoHotkey Script Execution from User Writable Path by DarkGate
Malicious China Chopper Web Shell Command Pattern in IIS Worker Process (via process_creation)
Malicious AutoHotKey Runner AutoNotify Executing AHKBot Looper Script (via process_creation)
Malicious IIS Worker Process Spawning Command Shell after ASP.NET ViewState Injection (via process_creation)
Suspicious MSSQL xp_cmdshell Enablement via sp_configure (via process_creation)
Windows forfiles.exe Execution with /c Flag Command Proxying
Pivot detection · T1059 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

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