huntrule

Windows Registry Startup: Chrome VPN Extensions Installed via Extension Registry Keys

Flags Windows Registry updates that register VPN/proxy Chrome extensions via the Chrome Extensions update_url key.

FreeReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
frack113 (SigmaHQ), DRL 1.1
Published
2021-12-28
Updated
2026-07-30
AnalysisDetection

ATT&CK techniques

Initial Access → Persistence

  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 identifies when Google Chrome extensions that provide VPN/proxy functionality are registered through Windows Registry entries under the Chrome Extensions update_url path. Attackers may use Chrome extensions to establish persistent network routing and conceal traffic by automating extension installation or configuration. The rule relies on Windows Registry set telemetry by matching specific Chrome extension TargetObject identifiers and confirming the Registry location ends with update_url under the Chrome 32-bit extension path.

Reporting behind it

Related detections9 linkedT1133 — drag to rearrange
Suspicious Reverse SSH Tunnel Creation with Host Key Verification Disabled (via process_creation)
Suspicious Shell Script Execution From Temp Directory on SonicWall SMA1000 Appliance (via process_creation)
Possible PAN-OS CVE-2026-0257 Exploitation via GlobalProtect PoC Artifacts (via network)
Possible RD Web Access Brute Force via Repeated Login POST Requests
Suspicious Security Group Ingress Rule Opened to the Internet via CloudTrail
SplashTop Network
Suspicious SoftEther VPN Hamcore Config Written to ProgramData (via file_event)
SplashTop Process
AnyDesk Network
Windows Registry Startup: Chrome VPN Extensions Installed via Extension Registry Keys
Pivot detection · T1133 · 9 related

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