Suspicious Microsoft Edge Native Messaging Host Registration via UNC6692

PremiumReviewedSigma · Medium · v1
Category
registry_set
Author
HuntRule
Published
2026-09-23
Updated
2026-09-23

ATT&CK techniques

Persistence
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects registration of a Microsoft Edge native messaging host, the mechanism UNC6692 uses to bridge its sideloaded extension to a local Python messaging host. This channel lets the browser extension execute native code and communicate with attacker tooling. New native messaging host registrations should be validated against known browser integrations.

Related detections9 linkedT1176 — drag to rearrange
Suspicious Chrome Malicious Extension Deployment via StormBamboo
Suspicious Browser Launch with Unpacked Extension Loaded via load-extension (via process_creation)
Malicious GenAI Browser Extension C2 and PAC Redirection (via proxy)
Suspicious Microsoft Edge Headless Launch with Unpacked Extension via SNOWBELT (via process_creation)
Suspicious Browser Extension Force-Install via Registry (via registry_set)
Malicious Madgicx Plus Chrome Extension Identifiers on Disk
Suspicious Browser Extension Sideload From a User Path (via process_creation)
Suspicious Chrome Remote Debugging Port for Browser Session Theft
Suspicious Microsoft Edge Unpacked Extension Load via UNC6692 Edgecution
Suspicious Microsoft Edge Native Messaging Host Registration via UNC6692
Pivot detection · T1176 · 9 related

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