This site has been deprecated in favor of and will remain in place until 11/1/22.


From attackics
Jump to navigation Jump to search

To visit this technique’s new page please go to and update your links to

ID T0853
Tactic Execution
Data Sources Command: Command Execution, Module: Module Load, Process: Process Creation, Script: Script Execution
Asset Engineering Workstation


Adversaries may use scripting languages to execute arbitrary code in the form of a pre-written script or in the form of user-supplied code to an interpreter. Scripting languages are programming languages that differ from compiled languages, in that scripting languages use an interpreter, instead of a compiler. These interpreters read and compile part of the source code just before it is executed, as opposed to compilers, which compile each and every line of code to an executable file. Scripting allows software developers to run their code on any system where the interpreter exists. This way, they can distribute one package, instead of precompiling executables for many different systems. Scripting languages, such as Python, have their interpreters shipped as a default with many Linux distributions.

In addition to being a useful tool for developers and administrators, scripting language interpreters may be abused by the adversary to execute code in the target environment. Due to the nature of scripting languages, this allows for weaponized code to be deployed to a target easily, and leaves open the possibility of on-the-fly scripting to perform a task.

Procedure Examples

  • APT33 utilized PowerShell scripts to establish command and control and install files for execution.12
  • Dragonfly 2.0 deleted indicators on staging and target devices by uninstalling software, removing event logs, batch scripts, screenshots, registry keys, documents, and tools they brought into the target networks.3
  • HEXANE utilizes VBA macros and Powershell scripts such as DanDrop and kl.ps1 tools.45
  • OilRig has embedded a macro within spearphishing attachments that has been made up of both a VBScript and a PowerShell script.6
  • Sandworm Team utilized VBS and batch scripts for file movement and as wrappers for PowerShell execution.7
  • REvil utilizes JavaScript, WScript, and PowerShell scripts to execute. The malicious JavaScript attachment has an obfuscated PowerShell script that executes the malware.8
  • Triton communicates with Triconex controllers using a custom component framework written entirely in Python. The modules that implement the TriStation communication protocol and other supporting components are found in a separate file -- -- the main script that employs this functionality is compiled into a standalone py2exe Windows executable -- trilog.exe – which includes a Python environment.9


  • Application Isolation and Sandboxing - Consider the use of application isolation and sandboxing to restrict specific operating system interactions such as access through user accounts, services, system calls, registry, and network access. This may be even more useful in cases where the source of the executed script is unknown.
  • Disable or Remove Feature or Program - Consider removal or disabling of programs and features which may be used to run malicious scripts (e.g., scripting language IDEs, PowerShell, visual studio).
  • Execution Prevention - Execution prevention may prevent malicious scripts from accessing protected resources.