Suspicious MicrosoftEdgeUpdate Launched with Dat Config File

PremiumReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-10-21
Updated
2026-10-21

ATT&CK techniques

Execution → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects MicrosoftEdgeUpdate.exe being started with a --config argument pointing at a .dat file, a pattern the legitimate Edge updater never uses. The Vidar campaign abuses the trusted Edge updater name to sideload a payload configured from a data file such as mgwthmc2.dat. Detecting this unusual argument reveals a masqueraded loader riding a signed updater filename.

Related detections9 linkedT1036.005 — drag to rearrange
Malicious G DATA Avk.exe Masquerading From Public Folder via PlugX (via process_creation)
Suspicious msinfo32.exe Executed From ViPNet Update Directory
Suspicious MsMpEng Execution from Non-Standard Directory
Suspicious Svchost Execution from Non-System Path
Windows ImageLoad of Unsigned .node Native Add-on Files
Malicious Scheduled Task Masquerading as Defender NisSrv via Schtasks
Malicious PowerShell Masquerading as Windows Terminal in ProgramData (via process_creation)
Suspicious GoogleUpdate Binary Executing From Non-Standard Path (via process_creation)
Suspicious Csrss Process Masquerading Outside System32 (via process_creation)
Suspicious MicrosoftEdgeUpdate Launched with Dat Config File
Pivot detection · T1036.005 · 9 related

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