Command and Scripting Interpreter (T1059)

Tactic: Execution · Platforms: Containers, ESXi, IaaS, Identity Provider, Linux, macOS, Network Devices, Office Suite, SaaS, Windows

The interactive view maps 1 detection strategy, 9 mitigations, 17 threat groups, 23 software entries, 4 campaigns to this technique, alongside D3FEND countermeasures and data-component coverage.

Overview

Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries. These interfaces and languages provide ways of interacting with computer systems and are a common feature across many different platforms. Most systems come with some built-in command-line interface and scripting capabilities, for example, macOS and Linux distributions include some flavor of Unix Shell while Windows installations include the Windows Command Shell and PowerShell.

There are also cross-platform interpreters such as Python, as well as those commonly associated with client applications such as JavaScript and Visual Basic.

Adversaries may abuse these technologies in various ways as a means of executing arbitrary commands. Commands and scripts can be embedded in Initial Access payloads delivered to victims as lure documents or as secondary payloads downloaded from an existing C2. Adversaries may also execute commands through interactive terminals/shells, as well as utilize various Remote Services in order to achieve remote Execution.

Sub-techniques

• PowerShell (T1059.001)
• AppleScript (T1059.002)
• Windows Command Shell (T1059.003)
• Unix Shell (T1059.004)
• Visual Basic (T1059.005)
• Python (T1059.006)
• JavaScript (T1059.007)
• Network Device CLI (T1059.008)
• Cloud API (T1059.009)
• AutoHotKey & AutoIT (T1059.010)
• Lua (T1059.011)
• Hypervisor CLI (T1059.012)
• Container CLI/API (T1059.013)

Explore

• Open T1059 in the interactive ATT&CK matrix
• ATT&CK Intelligence View guide
• Official MITRE ATT&CK entry for T1059
• Sigma detection rules for MITRE ATT&CK
• Built by Shahrukh Khan