Suspicious Run Key Masquerading as GoogleUpdate From Wrong Path via Registry Set (via registry_set)

PremiumReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-08-14
Updated
2026-08-28

ATT&CK techniques

Persistence → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Cred Access

  6. Discovery

  7. Lateral Movement

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule detects a Run key autostart entry masquerading as GoogleUpdate but pointing to a payload outside the legitimate Google update directory, a persistence and masquerading technique used by malware from MSIX installers per Red Canary. A trusted-looking name paired with the wrong file path is a high-confidence indicator of a malicious autorun disguised as software updater.

Related detections9 linkedT1547.001 — drag to rearrange
LeakyStealer Persistence via EdgeUpdateCore Run Key Masquerade (via registry_set)
Suspicious SugarGh0st Persistence via CTFMON Masqueraded Run Key (via registry_set)
Malicious MicrosoftUpdate Run Key Persistence via Axios Compromise
Suspicious Service NetDnsActivatorSharing Creation via Process Creation
Xeno Stealer Persistence via Display Calibration Run Key
Suspicious Node.js Script Execution from AppData Roaming
Suspicious AutoAdminLogon Enabled via Winlogon Registry by RansomHub Ransomware
Suspicious PlugX Persistence via CanonPrinter Run Key (via registry_set)
Malicious Fake Fortinet Patch Infostealer Execution (via process_creation)
Suspicious Run Key Masquerading as GoogleUpdate From Wrong Path via Registry Set (via registry_set)
Pivot detection · T1547.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.