命令与脚本解释器

APT19 downloaded and launched code within a SCT file.^[1]

APT32 has used COM scriptlets to download Cobalt Strike beacons.^[2]

APT37 has used Ruby scripts to execute payloads.^[3]

APT39 has utilized custom scripts to perform internal reconnaissance.^[4][5]

Bandook can support commands to execute Java-based payloads.^[6]

Bonadan can create bind and reverse shells on the infected system.^[7]

CHOPSTICK is capable of performing remote command execution.^[8][9]

During Cutting Edge, threat actors used Perl scripts to enable the deployment of the THINSPOOL shell script dropper and for enumerating host data.^[10][11]

DarkComet can execute various types of scripts on the victim’s machine.^[12]

Donut can generate shellcode outputs that execute via Ruby.^[13]

Dragonfly has used the command line for execution.^[14]

Empire uses a command-line interface to interact with systems.^[15]

FIN5 scans processes on all victim systems in the environment and uses automated scripts to pull back the results.^[16]

FIN6 has used scripting to iterate through a list of compromised PoS systems, copy data to a log file, and remove the original data files.^[17][18]

FIN7 used SQL scripts to help perform tasks on the victim's machine.^[19][20][19]

FIVEHANDS can receive a command line argument to limit file encryption to specified directories.^[21][22]

Fox Kitten has used a Perl reverse shell to communicate with C2.^[23]

Get2 has the ability to run executables with command-line arguments.^[24]

gh0st RAT is able to open a remote shell to execute commands.^[25][26]

Imminent Monitor has a CommandPromptPacket and ScriptPacket module(s) for creating a remote shell and executing scripts.^[27]

Malware used by Ke3chang can run commands on the command-line interface.^[28][29]

Kessel can create a reverse shell between the infected host and a specified system.^[7]

Matryoshka is capable of providing Meterpreter shell access.^[30]

OilRig has used various types of scripting for execution.^{[31][32][33][34][35]}

For Operation Spalax, the threat actors used Nullsoft Scriptable Install System (NSIS) scripts to install malware.^[36]

P.A.S. Webshell has the ability to create reverse shells with Perl scripts.^[37]

Raspberry Robin variants can be delivered via highly obfuscated Windows Script Files (WSF) for initial execution.^[38]

Saint Bear has used the Windows Script Host (wscript) to execute intermediate files written to victim machines.^[39]

SLIGHTPULSE contains functionality to execute arbitrary commands passed to it.^[40]

SpeakUp uses Perl scripts.^[41]

Stealth Falcon malware uses WMI to script data collection and command execution on the victim.^[42]

VersaMem was delivered as a Java Archive (JAR) that runs by attaching itself to the Apache Tomcat Java servlet and web server.^[43]

Whitefly has used a simple remote shell tool that will call back to the C2 server and wait for commands.^[44]

Windigo has used a Perl script for information gathering.^[7]

WINERACK can create a reverse shell that utilizes statically-linked Wine cmd.exe code to emulate Windows command prompt commands.^[45]

Winter Vivern used XLM 4.0 macros for initial code execution for malicious document files.^[46]

ZeroCleare can receive command line arguments from an operator to corrupt the file system using the RawDisk driver.^[47]

Zeus Panda can launch remote scripts on the victim’s machine.^[48]

Anti-virus can be used to automatically quarantine suspicious files.

Inventory systems for unauthorized command and scripting interpreter installations.

On Windows 10, enable Attack Surface Reduction (ASR) rules to prevent Visual Basic and JavaScript scripts from executing potentially malicious downloaded content ^[49].

Where possible, only permit execution of signed scripts.

Disable or remove any unnecessary or unused shells or interpreters.

Use application control where appropriate. For example, PowerShell Constrained Language mode can be used to restrict access to sensitive or otherwise dangerous language elements such as those used to execute arbitrary Windows APIs or files (e.g., Add-Type).^[50]

Prevent user installation of unrequired command and scripting interpreters.

When PowerShell is necessary, consider restricting PowerShell execution policy to administrators. Be aware that there are methods of bypassing the PowerShell execution policy, depending on environment configuration.^[51]

PowerShell JEA (Just Enough Administration) may also be used to sandbox administration and limit what commands admins/users can execute through remote PowerShell sessions.^[52]

Script blocking extensions can help prevent the execution of scripts and HTA files that may commonly be used during the exploitation process. For malicious code served up through ads, adblockers can help prevent that code from executing in the first place.