Detect MMC in Elastic Security
Adversaries may abuse mmc.exe to proxy execution of malicious .msc files. Microsoft Management Console (MMC) is a signed Microsoft binary used to create, open, and save custom consoles containing administrative snap-ins. Adversaries can craft malicious .msc files that execute arbitrary commands when opened in MMC. The Medusa ransomware group has been documented using this technique. MMC snap-ins can execute commands, run scripts, and perform system administration actions, making malicious .msc files a powerful execution vehicle that bypasses application control.
MITRE ATT&CK
- Tactic
- Defense Evasion
- Technique
- T1218 System Binary Proxy Execution
- Sub-technique
- T1218.014 MMC
- Canonical reference
- https://attack.mitre.org/techniques/T1218/014/
Elastic Detection Query
sequence by host.name with maxspan=5m
[process where event.type == "start" and process.name : "mmc.exe" and
(
(process.args : "*.msc" and process.args : ("*Temp*", "*AppData*", "*Downloads*", "*Public*", "*Desktop*", "*ProgramData*")) or
process.args : ("http://*", "https://*", "\\\\*") or
process.parent.name : ("cmd.exe", "powershell.exe", "wscript.exe", "cscript.exe", "mshta.exe", "winword.exe", "excel.exe", "outlook.exe")
)
] by process.pid
[process where event.type == "start" and
process.parent.name : "mmc.exe" and
process.name : ("cmd.exe", "powershell.exe", "wscript.exe", "cscript.exe", "net.exe", "netsh.exe")
] by process.parent.pidDetects MMC.exe abuse for T1218.014 — matches MMC loading .msc files from suspicious paths, loading remote .msc files, being spawned by script interpreters or Office apps, or spawning suspicious child processes. Uses EQL sequence correlation to link parent MMC execution to child process spawning.
Data Sources
Required Tables
False Positives & Tuning
- Legitimate IT administrators opening custom .msc consoles stored in user profile directories such as AppData for convenience
- Software deployment tools (SCCM, Ansible, PDQ Deploy) that invoke mmc.exe with .msc files from temp staging directories
- Help desk or remote support workflows that programmatically launch MMC snap-ins via cmd.exe or PowerShell for automated configuration tasks
Other platforms for T1218.014
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.
- Test 1MMC Execution with Custom MSC File from Temp
Expected signal: Sysmon Event ID 11: .msc file written to Temp. Sysmon Event ID 1: mmc.exe with Temp path in command line. Security Event ID 4688.
- Test 2MMC Launched from PowerShell
Expected signal: Sysmon Event ID 1: powershell.exe then mmc.exe with ParentImage=powershell.exe. SuspiciousParent fires. Security Event ID 4688.
- Test 3MMC Child Process Spawning
Expected signal: If a real malicious snap-in were loaded, Sysmon EventCode=1 would show cmd.exe or powershell.exe with ParentImage=mmc.exe. This test generates the mmc.exe process creation event for detection validation.
References (4)
Unlock Pro Content
Get the full detection package for T1218.014 including response playbook, investigation guide, and atomic red team tests.