Suspicious LucidRook DLL Side-Loading via Renamed msedge.exe

PremiumReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-05-17
Updated
2026-08-28

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 detects msedge.exe executing from a WindowsApps directory under the user profile, matching the LucidRook loader that renames the DISM index.exe binary to msedge.exe to side-load a malicious DismCore.dll. Legitimate Microsoft Edge runs from Program Files, so an msedge.exe launched from AppData WindowsApps is an impostor used for search-order hijacking. This behavior indicates initial execution of the Lua-based LucidRook malware.

Related detections9 linkedT1574.001 — drag to rearrange
Suspicious DLL Sideload of profiler16.dll (via image_load)
Malicious PUBLOAD Fake Windows Update C2 Request via Proxy (via proxy)
Suspicious MicrosoftEdgeUpdate Launched with Dat Config File
Suspicious GoogleUpdate Binary Executing From Non-Standard Path (via process_creation)
Suspicious MpClient DLL Sideload from Non-Defender Path
Suspicious DLL Load From ProgramData Intel Sideload Path (via image_load)
Suspicious DLL Sideload of uevmonitor via SoftwareLicencing (via image_load)
Malicious DLL Side-Loading via 7z or clink Loaders
Malicious Gh0st RAT DLL Side-Loading via wsc_proxy Loading wsc.dll (via image_load)
Suspicious LucidRook DLL Side-Loading via Renamed msedge.exe
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.