Hijacked Browser Extensions: How Supply-Chain Takeovers Happen and How to Audit What You Have Installed
Extensions turn malicious through phished developer accounts and quiet ownership sales. Here is how both attacks work and a routine to audit your installs.
By Palancar · 5 min · 17 November 2026

Hijacked Browser Extensions: How Supply-Chain Takeovers Happen and How to Audit What You Have Installed
An extension you installed years ago and trust may not be the same software today. Extensions update silently, and the people behind them change. That combination is the supply-chain problem: the code you approved at install time is not necessarily the code running in your browser now. Two mechanisms account for most of the documented cases, a compromised developer account and a change of ownership.
Mechanism One: A Phished Developer Account
The clearest recent example is the Cyberhaven extension compromise in late December 2024. According to the company’s account, a developer listed as a public support contact received a phishing email posing as Chrome Web Store support and claiming the extension violated store policy. The link led to Google’s genuine authorization page, where the target approved a malicious OAuth application named “Privacy Policy Extension.”
Cyberhaven said the employee had Google Advanced Protection and multi-factor authentication enabled, and that no MFA prompt was triggered because the attack did not steal credentials. The OAuth grant itself gave the attacker permission to manage the developer’s extensions, including publishing. The attacker uploaded a modified build, and it reached users through Chrome’s normal update channel, reaching roughly 400,000 users according to reports. Cyberhaven said it detected and removed the update within an hour of discovery and shipped a clean version. The malicious code was reported to exfiltrate cookies, session tokens, and credentials, mainly for social-media advertising and AI platforms.
Researchers linked the same playbook to other extensions. Sources disagree on the total, with figures ranging from 16 extensions and over 600,000 users to at least 35 and over 2.6 million, so treat campaign-wide numbers as estimates. The lesson that holds regardless of the count: MFA did not stop an attack that abused an OAuth consent screen.
Mechanism Two: Ownership Changes
The second route needs no phishing. A developer sells a small extension, and the buyer inherits a trusted listing and an existing install base. Updates then apply without any user confirmation.
A 2026 case reported by researchers at Annex Security and an independent researcher involved two Chrome extensions, QuickLens (about 7,000 users) and ShotBird (about 800). QuickLens was listed for sale shortly after publication, and ownership reportedly moved to a new account on February 1, 2026. A malicious update followed on February 17. It kept its Google Lens function while stripping security headers such as X-Frame-Options from responses, and it requested a script from an external server every five minutes, with the payload held in local storage rather than the extension’s source files. ShotBird reportedly showed users a fake Chrome update prompt that led them to run a PowerShell command. The researchers attributed both to the same attacker, based on matching architecture and technique. The report did not say how the extensions were detected or whether the store has removed them, so check the current store status before citing it further.
The pattern is older than that: in 2014, extensions including Add to Feedly were sold and then updated to inject ads. The mechanism has not changed much since: a trusted listing changes hands, and the install base inherits whatever the new owner ships.
Why Both Attacks Work
Auto-update is a feature, and it is the delivery channel. A user’s consent happens once, at install, against a permission list. If the permissions already cover “read and change all your data on all websites,” a later malicious version needs no further prompt. Remote code loaded after install, like the QuickLens payload, also means a store review of the submitted package may not see the real behavior.
An Audit Routine You Can Run Today
- Inventory. Open your browser’s extensions page and list everything, including disabled items. Remove anything you do not recognize or have not used in months. The fewer installed, the smaller the surface.
- Check permissions, not names. For each remaining extension, look at the site access setting. Our Chrome extension permissions guide explains which permissions matter. Change “on all sites” to “on click” or specific sites where the extension allows it.
- Check the publisher. Look at the listing’s developer name and contact details. A recent change in publisher, a new support email, or a rewritten privacy policy on a long-established extension is worth investigating.
- Read the version history. Look for updates that add no described feature and for sudden permission increases, which the browser may surface as a re-approval prompt.
- Check update timing. Reported guidance suggests delaying auto-updates for 48 to 72 hours in managed environments, giving researchers time to catch a bad release. This requires enterprise tooling, so treat it as an option for IT teams, not an individual setting.
- Treat sessions as compromised if in doubt. If an extension you ran is later reported malicious, remove it, sign out everywhere, and rotate credentials, since stolen session tokens work without your password.
For Developers
Review third-party OAuth grants on your Google account regularly, treat any “policy violation” email as suspect until verified in the store dashboard, and use phishing-resistant sign-in. If you sell an extension, remember that you are handing over the update channel to your users’ browsers. The store’s evolving rules, covered in our piece on the Chrome Web Store data-collection policy, now require disclosure when data handling changes after installation.
The Takeaway
You cannot verify an extension once and trust it forever. Keep the list short, restrict site access, and revisit it on a schedule, because the realistic risk is not the extension you installed last week but the one that changed hands last month.