Adversaries may abuse msiexec.exe to proxy execution of malicious payloads. Msiexec.exe is the command-line utility for the Windows Installer and is thus commonly associated with executing installation packages (.msi).[1] The Msiexec.exe binary may also be digitally signed by Microsoft.
Adversaries may abuse msiexec.exe to launch local or network accessible MSI files. Msiexec.exe can also execute DLLs.[2][3] Since it may be signed and native on Windows systems, msiexec.exe can be used to bypass application control solutions that do not account for its potential abuse. Msiexec.exe execution may also be elevated to SYSTEM privileges if the AlwaysInstallElevated policy is enabled.[4]
| ID | Name | Description |
|---|---|---|
| C0057 | 3CX Supply Chain Attack |
During the 3CX Supply Chain Attack, AppleJeus delivered components using a Windows Installer package (.msi). The MSI installer extracted several files and executed the 3CXDesktopApp.exe, which loaded the malicious library file ffmpeg.dll.[5] |
| S0584 | AppleJeus | |
| G0082 | APT38 | |
| S0631 | Chaes |
Chaes has used .MSI files as an initial way to start the infection chain.[8] |
| S0611 | Clop |
Clop can use msiexec.exe to disable security tools on the system.[9] |
| S1052 | DEADEYE |
DEADEYE can use |
| S0038 | Duqu |
Duqu has used |
| S0381 | FlawedAmmyy |
FlawedAmmyy has been installed via |
| S0531 | Grandoreiro |
Grandoreiro can use MSI files to execute DLLs.[13] |
| S0483 | IcedID |
IcedID can inject itself into a suspended msiexec.exe process to send beacons to C2 while appearing as a normal msi application. [14] IcedID has also used msiexec.exe to deploy the IcedID loader.[15] |
| S0528 | Javali |
Javali has used the MSI installer to download and execute malicious payloads.[13] |
| S1160 | Latrodectus |
Latrodectus has called |
| S0451 | LoudMiner |
LoudMiner used an MSI installer to install the virtualization software.[18] |
| G0095 | Machete |
Machete has used msiexec to install the Machete malware.[19] |
| S0449 | Maze |
Maze has delivered components for its ransomware attacks using MSI files, some of which have been executed from the command-line using |
| S0530 | Melcoz |
Melcoz can use MSI files with embedded VBScript for execution.[13] |
| S0455 | Metamorfo |
Metamorfo has used MsiExec.exe to automatically execute files.[21][22] |
| S1122 | Mispadu | |
| G0021 | Molerats |
Molerats has used msiexec.exe to execute an MSI payload.[25] |
| S0650 | QakBot |
QakBot can use MSIExec to spawn multiple cmd.exe processes.[26] |
| S0481 | Ragnar Locker |
Ragnar Locker has been delivered as an unsigned MSI package that was executed with |
| G0075 | Rancor |
Rancor has used |
| S1130 | Raspberry Robin |
Raspberry Robin uses msiexec.exe for post-installation communication to command and control infrastructure.[29] Msiexec.exe is executed referencing a remote resource for second-stage payload retrieval and execution.[30] |
| S0662 | RCSession |
RCSession has the ability to execute inside the msiexec.exe process.[31] |
| C0047 | RedDelta Modified PlugX Infection Chain Operations |
Mustang Panda initial payloads downloaded a Windows Installer MSI file that in turn dropped follow-on files leading to installation of PlugX during RedDelta Modified PlugX Infection Chain Operations.[32] |
| S1240 | RedLine Stealer |
RedLine Stealer has been installed via MSI Installer.[33] |
| S0592 | RemoteUtilities |
RemoteUtilities can use Msiexec to install a service.[34] |
| G0092 | TA505 |
TA505 has used |
| G0128 | ZIRCONIUM |
ZIRCONIUM has used the msiexec.exe command-line utility to download and execute malicious MSI files.[38] |
| ID | Mitigation | Description |
|---|---|---|
| M1042 | Disable or Remove Feature or Program |
Consider disabling the |
| M1026 | Privileged Account Management |
Restrict execution of Msiexec.exe to privileged accounts or groups that need to use it to lessen the opportunities for malicious usage. |
| ID | Name | Analytic ID | Analytic Description |
|---|---|---|---|
| DET0158 | Detection of Msiexec Abuse for Local, Network, and DLL Execution | AN0445 |
Detection of msiexec.exe execution where command-line arguments reference remote MSI packages, UNC paths, HTTP/HTTPS URLs, or DLLs, correlated with subsequent module loads and/or network connections to previously unseen destinations. The behavioral chain links process creation of msiexec.exe with suspicious parameters, network activity to retrieve payloads, and module loading indicative of malicious installation or DLL execution. |