Real-world descriptions of how a group, tool or campaign used a technique.
1213 examples
| Technique | Used by | Procedure example |
|---|---|---|
| T1059.001 PowerShell |
CampaignPikabot Distribution February 2024 | Pikabot Distribution February 2024 passed execution from obfuscated JavaScript files to PowerShell scripts to download and install Pikabot. |
| T1059.001 PowerShell |
CampaignOperation AkaiRyū | During Operation AkaiRyū, MirrorFace used PowerShell in execution chains to drop additional files such as embedded CAB files. |
| T1059.001 PowerShell |
CampaignAPT28 Nearest Neighbor Campaign | During APT28 Nearest Neighbor Campaign, APT28 used PowerShell cmdlet |
| T1059.001 PowerShell |
Campaign2016 Ukraine Electric Power Attack | During the 2016 Ukraine Electric Power Attack, Sandworm Team used PowerShell scripts to run a credential harvesting tool in memory to evade defenses. |
| T1059.001 PowerShell |
CampaignOperation Wocao | During Operation Wocao, threat actors used PowerShell on compromised systems. |
| T1059.001 PowerShell |
Campaign2022 Ukraine Electric Power Attack | During the 2022 Ukraine Electric Power Attack, Sandworm Team utilized a PowerShell utility called TANKTRAP to spread and launch a wiper using Windows Group Policy. |
| T1059.001 PowerShell |
CampaignAI-Assisted Breach of Mexico's Government Infrastructure | During the AI-Assisted Breach of Mexico's Government Infrastructure, the adversary tasked Claude Code to use `ntlmrelay.py` to execute a base64-encoded PowerShell payload on five domain controllers. During the AI-Assisted Breach of Mexico's Government Infrastructure, the adversary utilized base64-encoded PowerShell payloads against victim servers. |
| T1059.003 Windows Command Shell |
CampaignOperation Dream Job | During Operation Dream Job, Lazarus Group launched malicious DLL files, created new folders, and renamed folders with the use of the Windows command shell. |
| T1059.003 Windows Command Shell |
CampaignSharePoint ToolShell Exploitation | During SharePoint ToolShell Exploitation, threat actors utilized `cmd.exe` and batch scripts within the victim environment. |
| T1059.003 Windows Command Shell |
CampaignFrankenstein | During Frankenstein, the threat actors ran a command script to set up persistence as a scheduled task named "WinUpdate", as well as other encoded commands from the command-line |
| T1059.003 Windows Command Shell |
CampaignOperation Honeybee | During Operation Honeybee, various implants used batch scripting and `cmd.exe` for execution. |
| T1059.003 Windows Command Shell |
CampaignWater Curupira Pikabot Distribution | Water Curupira Pikabot Distribution installation via JavaScript will launch follow-on commands via cmd.exe. |
| T1059.003 Windows Command Shell |
CampaignOperation Digital Eye | During Operation Digital Eye, threat actors used `cmd.exe` as a default method of execution for a custom version of Mimikatz named bK2o.exe. |
| T1059.003 Windows Command Shell |
CampaignC0015 | During C0015, the threat actors used `cmd.exe` to execute commands and run malicious binaries. |
| T1059.003 Windows Command Shell |
CampaignHomeLand Justice | During HomeLand Justice, threat actors used Windows batch files for persistence and execution. |
| T1059.003 Windows Command Shell |
CampaignSolarWinds Compromise | During the SolarWinds Compromise, APT29 used `cmd.exe` to execute commands on remote machines. |
| T1059.003 Windows Command Shell |
CampaignOperation AkaiRyū | During Operation AkaiRyū, MirrorFace used `cmd.exe` to run PowerShell commands to drop additional files on the compromised host. |
| T1059.003 Windows Command Shell |
CampaignFunnyDream | During FunnyDream, the threat actors used `cmd.exe` to execute the wmiexec.vbs script. |
| T1059.003 Windows Command Shell |
CampaignOperation CuckooBees | During Operation CuckooBees, the threat actors used batch scripts to perform reconnaissance. |
| T1059.003 Windows Command Shell |
CampaignAPT28 Nearest Neighbor Campaign | During APT28 Nearest Neighbor Campaign, APT28 used |
| T1059.003 Windows Command Shell |
Campaign2025 Poland Wiper Attacks | During the 2025 Poland Wiper Attacks, the adversaries leveraged PsExec to run `cmd.exe` commands on multiple victim machines. |
| T1059.003 Windows Command Shell |
Campaign2016 Ukraine Electric Power Attack | During the 2016 Ukraine Electric Power Attack, Sandworm Team used the `xp_cmdshell` command in MS-SQL. |
| T1059.003 Windows Command Shell |
CampaignNight Dragon | During Night Dragon, threat actors used zwShell to establish full remote control of the connected machine and run command-line shells. |
| T1059.003 Windows Command Shell |
CampaignOperation Wocao | During Operation Wocao, threat actors spawned a new `cmd.exe` process to execute commands. |
| T1059.003 Windows Command Shell |
CampaignC0017 | During C0017, APT41 used `cmd.exe` to execute reconnaissance commands. |
| T1059.004 Unix Shell |
CampaignKV Botnet Activity | KV Botnet Activity utilizes multiple Bash scripts during botnet installation stages, and the final botnet payload allows for running commands in the Bash shell. |
| T1059.004 Unix Shell |
CampaignRedPenguin | During RedPenguin, UNC3886 used malware capable of launching an interactive shell. |
| T1059.004 Unix Shell |
CampaignOperation MidnightEclipse | During Operation MidnightEclipse, threat actors piped output from stdout to bash for execution. |
| T1059.004 Unix Shell |
Campaign2025 Poland Wiper Attacks | During the 2025 Poland Wiper Attacks, the adversaries utilized the Linux `dd` command to overwrite portions of the disks with random data. |
| T1059.004 Unix Shell |
CampaignQuad7 Activity | Quad7 Activity has enabled the creation of an access-controlled command shell |
| T1059.004 Unix Shell |
CampaignFLORAHOX Activity | FLORAHOX Activity has executed multiple Bash controller scripts to provide command line inputs for FLORAHOX traversal configurations. |
| T1059.004 Unix Shell |
CampaignAI-Assisted Breach of Mexico's Government Infrastructure | During the AI-Assisted Breach of Mexico's Government Infrastructure, the adversary tasked Claude Code to execute various commands (e.g., `ls -la`, `nc`, `proxychains4`, etc.) and scripts (e.g., bash, etc.) using the Unix shell. |
| T1059.005 Visual Basic |
CampaignOperation Dream Job | During Operation Dream Job, Lazarus Group executed a VBA written malicious macro after victims download malicious DOTM files; Lazarus Group also used Visual Basic macro code to extract a double Base64 encoded DLL implant. |
| T1059.005 Visual Basic |
CampaignFrankenstein | During Frankenstein, the threat actors used Word documents that prompted the victim to enable macros and run a Visual Basic script. |
| T1059.005 Visual Basic |
CampaignOperation Sharpshooter | During Operation Sharpshooter, the threat actors used a VBA macro to execute a simple downloader that installed Rising Sun. |
| T1059.005 Visual Basic |
CampaignOperation Honeybee | For Operation Honeybee, the threat actors used a Visual Basic script embedded within a Word document to download an implant. |
| T1059.005 Visual Basic |
CampaignOperation Dust Storm | During Operation Dust Storm, the threat actors used Visual Basic scripts. |
| T1059.005 Visual Basic |
Campaign2015 Ukraine Electric Power Attack | During the 2015 Ukraine Electric Power Attack, Sandworm Team installed a VBA script called `vba_macro.exe`. This macro dropped `FONTCACHE.DAT`, the primary BlackEnergy implant; `rundll32.exe`, for executing the malware; `NTUSER.log`, an empty file; and desktop.ini, the default file used to determine folder displays on Windows machines. |
| T1059.005 Visual Basic |
CampaignC0015 | During C0015, the threat actors used a malicious HTA file that contained a mix of HTML and JavaScript/VBScript code. |
| T1059.005 Visual Basic |
CampaignJuicy Mix | During Juicy Mix, OilRig used VBS droppers to deliver and establish persistence for the Mango backdoor. |
| T1059.005 Visual Basic |
CampaignSolarWinds Compromise | For the SolarWinds Compromise, APT29 wrote malware such as Sibot in Visual Basic. |
| T1059.005 Visual Basic |
CampaignOperation AkaiRyū | During Operation AkaiRyū, MirrorFace used Word templates containing VBA code for malware execution. |
| T1059.005 Visual Basic |
CampaignFunnyDream | During FunnyDream, the threat actors used a Visual Basic script to run remote commands. |
| T1059.005 Visual Basic |
CampaignOperation CuckooBees | During Operation CuckooBees, the threat actors executed an encoded VBScript file using `wscript` and wrote the decoded output to a text file. |
| T1059.005 Visual Basic |
CampaignOuter Space | During Outer Space, OilRig used VBS droppers to deploy malware. |
| T1059.005 Visual Basic |
Campaign2016 Ukraine Electric Power Attack | During the 2016 Ukraine Electric Power Attack, Sandworm Team created VBScripts to run on an SSH server. |
| T1059.005 Visual Basic |
CampaignOperation Wocao | During Operation Wocao, threat actors used VBScript to conduct reconnaissance on targeted systems. |
| T1059.005 Visual Basic |
CampaignC0011 | For C0011, Transparent Tribe used malicious VBA macros within a lure document as part of the Crimson malware installation process onto a compromised host. |
| T1059.006 Python |
CampaignCutting Edge | During Cutting Edge, threat actors used a Python reverse shell and the PySoxy SOCKS5 proxy tool. |
| T1059.006 Python |
CampaignShadowRay | During ShadowRay, threat actors used the Python `pty` module to open reverse shells. |
Data from MITRE ATT&CK® (Enterprise). ATT&CK® is a registered trademark of The MITRE Corporation.