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 |
|---|---|---|
| S0584 | AppleJeus | |
| S0631 | Chaes |
Chaes has used .MSI files as an initial way to start the infection chain.[6] |
| S0611 | Clop |
Clop can use msiexec.exe to disable security tools on the system.[7] |
| S0038 | Duqu |
Duqu has used |
| S0531 | Grandoreiro |
Grandoreiro can use MSI files to execute DLLs.[9] |
| S0483 | IcedID |
IcedID can inject itself into a suspended msiexec.exe process to send beacons to C2 while appearing as a normal msi application. [10] |
| S0528 | Javali |
Javali has used the MSI installer to download and execute malicious payloads.[9] |
| S0451 | LoudMiner |
LoudMiner used an MSI installer to install the virtualization software.[11] |
| G0095 | Machete |
Machete has used msiexec to install the Machete malware.[12] |
| 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.[9] |
| S0455 | Metamorfo |
Metamorfo has used MsiExec.exe to automatically execute files.[14][15] |
| G0021 | Molerats |
Molerats has used msiexec.exe to execute an MSI payload.[16] |
| S0650 | QakBot |
QakBot can use MSIExec to spawn multiple cmd.exe processes.[17] |
| S0481 | Ragnar Locker |
Ragnar Locker has been delivered as an unsigned MSI package that was executed with |
| G0075 | Rancor |
Rancor has used |
| S0662 | RCSession |
RCSession has the ability to execute inside the msiexec.exe process.[20] |
| S0592 | RemoteUtilities |
RemoteUtilities can use Msiexec to install a service.[21] |
| G0092 | TA505 |
TA505 has used |
| G0128 | ZIRCONIUM |
ZIRCONIUM has used the msiexec.exe command-line utility to download and execute malicious MSI files.[25] |
| 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 | Data Source | Data Component |
|---|---|---|
| DS0017 | Command | Command Execution |
| DS0011 | Module | Module Load |
| DS0029 | Network Traffic | Network Connection Creation |
| DS0009 | Process | Process Creation |
Use process monitoring to monitor the execution and arguments of msiexec.exe. Compare recent invocations of msiexec.exe with prior history of known good arguments and executed MSI files or DLLs to determine anomalous and potentially adversarial activity. Command arguments used before and after the invocation of msiexec.exe may also be useful in determining the origin and purpose of the MSI files or DLLs being executed.