WindowsT1047

>wmic.exe

Windows Management Instrumentation Command-line (WMIC) provides a command-line interface for WMI. Abused for process execution, remote lateral movement, process creation, and running XSL stylesheets.

Default Executable Paths

C:\Windows\System32\wbem\WMIC.exe
C:\Windows\SysWOW64\wbem\WMIC.exe

Integrity & Metadata

Original Name: wmic.exe
File Version: 10.0.19041.1
Category Count: 1 weaponized patterns
Forensics & Triage Insight

Microsoft has deprecated WMIC in recent Windows 11 builds, making WMIC execution increasingly anomalous in modern environments.

Detection Engineering Notes

Detect wmic spawning processes ("process call create") or retrieving remote XSL files with "/format:http:".

Executive Summary & AI Quick Reference

High-Fidelity Telemetry Profile

wmic.exe is a native utility pre-installed on Windows systems. Threat actors and red teams abuse wmic.exe as a Living-off-the-Land Binary (LOLBin) to achieve Execute without triggering traditional antivirus file-hash alerts. Legitimate system administrators use it for routine administration, making behavioral command-line telemetry essential for differentiation.

Primary Abused Tactics
Execute
Minimum Privilege
Administrator
Key Telemetry Source
Sysmon 1 / 4688
ATT&CK Mapping
T1047

Weaponized Parameters & Proof-of-Concepts

Documented attack commands, parameter flags, and privilege prerequisites.

1 documented methods
Filter Purpose:
ExecutePrivileges: Administrator
T1047: Windows Management Instrumentation

Abuses WMIC process call create to launch child processes with WmiPrvSE.exe as parent, breaking normal process lineage.

wmic.exe process call create "powershell.exe -w hidden -enc ..."

SIEM & EDR Detection Rules

Production telemetry rules configured for Microsoft Defender, Sigma, and Splunk.

Telemetry & SIEM Detection Suite (wmic.exe)

Validated against MITRE T1047
wmic.exe Microsoft Defender Querykql
1DeviceProcessEvents
2| where FileName =~ "wmic.exe"
3| where ProcessCommandLine has_all ("process", "call", "create")
4| project Timestamp, DeviceName, AccountName, InitiatingProcessFileName, ProcessCommandLine

Mitigation, Hardening & Prevention

Recommended defensive controls to block or constrain wmic.exe abuse.

Application Whitelisting

Enforce Windows Defender Application Control (WDAC) or AppLocker publisher rules to prevent execution outside approved enterprise administration scripts.

Attack Surface Reduction

Enable ASR rules: Block executable content from email client and webmail and Block Office applications from creating child processes spawning wmic.exe.

Behavioral Alerting

Deploy the KQL, Sigma, and Splunk detection queries below. Alert on anomalous child processes, web requests to unrated external IPs, or encoded payload strings.

Frequently Asked Questions (FAQ) • wmic.exe

Key operational questions and defensive answers about wmic.exe LOLBin tradecraft.

What is wmic.exe and why is it classified as a LOLBin?

wmic.exe is a legitimate, pre-installed or trusted utility on Windows. It is classified as a Living-off-the-Land Binary (LOLBin) because adversaries abuse its built-in functionality to perform malicious operations—such as Execute—without dropping custom malware binaries on disk.

How do threat actors abuse wmic.exe in cyber intrusions?

Adversaries leverage wmic.exe to execute stealthy actions while evading signature-based security controls. For example, attackers execute commands like "wmic.exe process call create "powershell.exe -w hidden -enc ..."" to achieve Execute, masquerading behind legitimate system process lineage.

How can SOC analysts detect suspicious wmic.exe activity?

Detection engineers monitor process creation events (Windows Event ID 4688 or Sysmon Event ID 1; Linux auditd EXECVE; macOS Endpoint Security) inspecting anomalous command line arguments, unusual parent-child process relationships (e.g. Office apps or web servers spawning wmic.exe), and unexpected network connections.

What MITRE ATT&CK techniques does wmic.exe map to?

wmic.exe maps to MITRE ATT&CK technique(s): T1047. These techniques cover adversary actions across tactics such as Defense Evasion, Execution, Persistence, and Command and Control.

How can organizations mitigate and restrict wmic.exe?

Mitigation strategies include implementing Application Control policies (AppLocker or Windows Defender Application Control - WDAC), enforcing Attack Surface Reduction (ASR) rules, configuring strict privilege separation (disallowing standard users from running sensitive switches), and alerting on execution from non-standard directories.

Sharon Ben Moshe
Curated & Verified by
Sharon Ben Moshe
Cybersecurity Researcher & Detection EngineerCheck Point