huntrule

Windows: Xwizard.exe Execution from Non-Default Directory

Alerts when Xwizard.exe starts from an unexpected Windows path, indicating potential misuse or side-loading.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Christian Burkard (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-09-20
Updated
2026-07-30
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 where Xwizard.exe is run from a directory outside the standard Windows locations (System32, SysWOW64, or WinSxS). Attackers may use this behavior to run the tool from an unexpected path, which can support malicious side-loading or other stealthy execution workflows. It relies on Windows process creation telemetry fields for Image (path/filename) and OriginalFileName to identify Xwizard.exe and apply the location exclusions.

Reporting behind it

Related detections9 linkedT1574.001 — drag to rearrange
Suspicious Service DLL Hijack of IKEEXT or PrintNotify
Malicious PowerShell Spawned by Masqueraded NVIDIA GeForce Experience Binary
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)
Windows: Xwizard.exe Execution from Non-Default Directory
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.