T1218.007 Elastic Security · Elastic

Detect Msiexec in Elastic Security

Adversaries may abuse msiexec.exe to proxy execution of malicious payloads. Msiexec.exe is the command-line utility for the Windows Installer and is commonly associated with executing installation packages (.msi). Since it is a signed Microsoft binary, msiexec.exe can bypass application control solutions. Adversaries use it to launch local or remote MSI files and to execute DLLs. Execution may also be elevated to SYSTEM if the AlwaysInstallElevated policy is enabled. Widely abused by malware families including QakBot, IcedID, Emotet, Clop, Maze, Ragnar Locker, Latrodectus, Raspberry Robin, TA505, Rancor, ZIRCONIUM, and many others.

MITRE ATT&CK

Tactic
Defense Evasion
Technique
T1218 System Binary Proxy Execution
Sub-technique
T1218.007 Msiexec
Canonical reference
https://attack.mitre.org/techniques/T1218/007/

Elastic Detection Query

Elastic Security (Elastic)
eql
process where event.type == "start"
  and process.name : "msiexec.exe"
  and (
    process.command_line : ("*http://*", "*https://*", "*ftp://*")
    or process.command_line : "* /y *"
    or (
      process.command_line : ("*/q *", "*/quiet *", "*/passive *")
      and process.command_line : ("*Temp*", "*AppData*", "*Downloads*", "*Public*", "*Desktop*")
    )
    or process.parent.name : ("cmd.exe", "powershell.exe", "wscript.exe", "cscript.exe", "mshta.exe", "winword.exe", "excel.exe", "outlook.exe")
  )
high severity high confidence

Detects T1218.007 msiexec.exe abuse for proxy execution using Elastic Common Schema process events. Identifies remote MSI loading via URL schemes, DLL registration via /y flag, silent installs from suspicious staging directories, and execution spawned from Office or scripting engine parent processes. Covers malware families including QakBot, IcedID, Emotet, and Latrodectus.

Data Sources

Elastic Defend (Endpoint Security)Winlogbeat with Sysmon moduleElastic Agent with Windows integration

Required Tables

logs-endpoint.events.process-*winlogbeat-*.ds-logs-windows.sysmon_operational-*

False Positives & Tuning

  • Enterprise software deployment via SCCM, Intune, or PDQ Deploy that silently installs MSI packages from internal HTTP artifact repositories or UNC share staging paths under AppData
  • IT automation frameworks (Ansible, Chef, Puppet) wrapping msiexec with /quiet flags and staging installers in %TEMP% or %PUBLIC% before execution
  • Legitimate patch management agents (Ivanti Neurons, ManageEngine Patch Manager) that spawn msiexec from PowerShell helper scripts with silent install flags
Download portable Sigma rule (.yml)

Other platforms for T1218.007


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Msiexec Remote MSI Execution

    Expected signal: Sysmon Event ID 1: msiexec.exe with URL and /q flag. Sysmon Event ID 3: Network connection attempt to 127.0.0.1:8080. Security Event ID 4688. The installation will fail (no server) but the process creation event fires.

  2. Test 2Msiexec DLL Execution via /y Flag

    Expected signal: Sysmon Event ID 11: DLL written to Temp. Sysmon Event ID 1: msiexec.exe with /y flag and Temp path. Sysmon Event ID 7 (Image Load) for the DLL being loaded by msiexec.

  3. Test 3Msiexec Silent Install from Temp Directory via PowerShell

    Expected signal: Sysmon Event ID 1: powershell.exe, then msiexec.exe with /q and Temp path, ParentImage=powershell.exe. Both SuspiciousParent and SuspiciousPath fire. Security Event ID 4688 for both.

Unlock Pro Content

Get the full detection package for T1218.007 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections