Windows Process Creation: Renamed Mavinject32/64.EXE Execution

Alerts on renamed executions of mavinject32.exe/mavinject64.exe based on OriginalFileName and image path.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
frack113, Florian Roth (SigmaHQ), DRL 1.1
Published
2022-12-05
Updated
2026-07-30

ATT&CK techniques

Priv Esc → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule flags process execution where the binary’s OriginalFileName matches mavinject32.exe or mavinject64.exe, excluding cases where the image path ends with the original filename. Attackers can use renamed legitimate utilities to help carry out stealthy process injection workflows, especially when invoking functionality through specific command-line flags. The rule relies on Windows process creation telemetry fields for OriginalFileName and Image path.

Related detections9 linkedT1055.001 — drag to rearrange
Suspicious Process Injection via mavinject INJECTRUNNING
Windows Process Injection via Mavinject Using INJECTRUNNING Flag
In-Memory Process Injection via Mavinject INJECTRUNNING (via process_creation)
Suspicious Service Reconfiguration of SessionEnv or IKEEXT for DLL Injection by EAGERBEE
Windows Process Execution and DLL Injection via Tracker.exe
Windows TAIDOOR RAT DLL Load via rundll32 Command Line
Windows renamed dctask64.exe execution via known IMPHASH values
Windows Process Creation: Detect dctask64.exe with Endpoint Central Execution/Injection Flags
Windows CreateRemoteThread with LoadLibraryA likely DLL injection
Windows Process Creation: Renamed Mavinject32/64.EXE Execution
Pivot detection · T1055.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.