Suspicious Renamed MonitoringHost Binary Indicating DLL Side-Loading

PremiumReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-06-22
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 execution of the signed Microsoft MonitoringHost binary under a renamed file name, a technique used by the SADBRIDGE loader to deploy the GOSAR (Golang QUASAR) backdoor. SADBRIDGE renames MonitoringHost.exe to DevQueryBroker.exe and abuses DLL search order hijacking to side-load a malicious HealthServiceRuntime.dll. Detecting a mismatch between the original file name and the on-disk image name surfaces this masquerading and side-loading activity for triage.

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 Renamed MonitoringHost Binary Indicating DLL Side-Loading
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.