Windows vmnat.exe Renamed Execution for Possible DLL Side-Loading

Alerts on Windows processes where vmnat.exe appears renamed, which may support stealthy execution and DLL side-loading behavior.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
elhoim (SigmaHQ), DRL 1.1
Published
2022-09-09
Updated
2026-07-30

ATT&CK techniques

Execution → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags process creation events where an executable image ending in "vmnat.exe" was renamed from the original file name identifier "vmnat.exe". Renamed binaries can be used to disguise execution and potentially facilitate DLL side-loading by launching a trusted-looking executable under an altered name. The detection relies on Windows process creation telemetry and the executable file metadata fields indicating the original file name versus the observed image name.

Related detections9 linkedT1574.001 — drag to rearrange
Suspicious msimg32.dll Loaded from Non-System Directory
DLL Side-Loading via Signed Binary Loading Known Malicious Helper DLL
Suspicious DLL Sideloading via msdtc oci.dll Install (via process_creation)
Suspicious wmicodegen.dll Sideload by inetinfo.exe (UAT-8099 Cobalt Strike)
Suspicious LucidRook DismCore.dll Side-Load into Browser Process
Suspicious Encrypted Implant File Creation for DLL Search Order Hijacking (RainyDay Turian PlugX)
Suspicious RoboForm Signed Binary Executed From Non-Standard Path (via process_creation)
Malicious dal_keepalives.dll Sideloaded By Signed Binary (via image_load)
Suspicious Cortex XDR Binary Sideloading winutils.dll (via image_load)
Windows vmnat.exe Renamed Execution for Possible DLL Side-Loading
Pivot detection · T1574.001 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.