Indirect Command Execution

Adversaries may abuse utilities that allow for command execution to bypass security restrictions that limit the use of command-line interpreters. Various Windows utilities may be used to execute commands, possibly without invoking cmd. For example, Forfiles, the Program Compatibility Assistant (pcalua.exe), components of the Windows Subsystem for Linux (WSL), as well as other utilities may invoke the execution of programs and commands from a Command and Scripting Interpreter, Run window, or via scripts. [1] [2]

Adversaries may abuse these features for Defense Evasion, specifically to perform arbitrary execution while subverting detections and/or mitigation controls (such as Group Policy) that limit/prevent the usage of cmd or file extensions more commonly associated with malicious payloads.

ID: T1202
Sub-techniques:  No sub-techniques
Tactic: Defense Evasion
Platforms: Windows
Permissions Required: User
Data Sources: File monitoring, Process command-line parameters, Process monitoring, Windows event logs
Defense Bypassed: Application control, Application control by file name or path, Static File Analysis
Contributors: Matthew Demaske, Adaptforward
Version: 1.1
Created: 18 April 2018
Last Modified: 20 June 2020

Procedure Examples

Name Description

Forfiles can be used to subvert controls and possibly conceal command execution by not directly invoking cmd.[1][2]

Revenge RAT

Revenge RAT uses the Forfiles utility to execute commands on the system.[3]


This type of attack technique cannot be easily mitigated with preventive controls since it is based on the abuse of system features.


Monitor and analyze logs from host-based detection mechanisms, such as Sysmon, for events such as process creations that include or are resulting from parameters associated with invoking programs/commands/files and/or spawning child processes/network connections. [4]