huntrule

Windows: Detect VMwareXferlogs.exe Executed from Non-default Path

Alert on VMwareXferlogs.exe launching from an unexpected directory, a potential DLL sideloading technique on Windows.

FreeReviewedSigma · High · v2
Product
windows
Category
process_creation
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-08-02
Updated
2026-07-31
AnalysisDetection

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 VMware Xfer utility (VMwareXferlogs.exe) runs from a directory outside the expected default VMware installation path. Attackers may use legitimate VMware utilities placed or launched from non-standard locations to load malicious DLLs or persist while blending in with trusted tooling. It relies on Windows process creation telemetry, matching the executable filename suffix and excluding the typical installation directory prefix.

Reporting behind it

Related detections9 linkedT1574.001 — drag to rearrange
Suspicious BugSplat Binary Sideloading bugsplatrc.dll via DLL Search Order Hijack
Suspicious SentinelOne Binary Sideloading sentinelagentcore.dll
Suspicious 7-Zip Executable Sideloading 7z.dll Loader
Suspicious Loading of Masqueraded EndpointDlp.dll Backdoor
Suspicious Trend Micro Binary Sideloading tmdglog.dll
Suspicious DLL Sideloading via ProtonVPN Executable (via image_load)
Suspicious DLL Sideloading via OneDriveStandaloneUpdater (via image_load)
Malicious HUI Loader DLL Side-Loading via McAfee mfeann.exe (via image_load)
Suspicious HUI Loader Configuration Artifact Creation via hellokety.ini (via file_event)
Windows: Detect VMwareXferlogs.exe Executed from Non-default Path
Pivot detection · T1574.001 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

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