When Google finalized the transition to Manifest V3 (MV3) across the Chromium ecosystem, the primary security justification was the elimination of remotely hosted code. By requiring all browser extension logic to be packaged statically and executed within isolated background service workers, Google promised that malicious extension updates could no longer download remote payloads to hijack consumer browsers.
However, late 2026 threat intelligence reports have exposed a sophisticated new supply-chain attack vector: MV3 OAuth Session Hijacking. By weaponizing benign extensions through developer account takeovers or legitimate cross-origin storage permissions, threat actors are covertly extracting authenticated OAuth 2.0 bearer tokens and session refresh cookies for services like Google Workspace, GitHub, and AWS Console. Here is how the attack functions and how to secure your browser.
1. The Vulnerability Vector: Service Workers & Cross-Origin Cookies
Under Manifest V3, extensions can still legitimately request broad host permissions (such as *://*.github.com/* or *://*.google.com/*) alongside the cookies or declarativeNetRequest permissions. The attack chain unfolds in four precise stages:
- Supply-Chain Acquisition: Cybercriminals purchase an established, highly rated utility extension (e.g. a color picker, screenshot tool, or volume booster with 200,000+ active users) or compromise the developer's Web Store credentials via spear-phishing.
- Benign Update Approval: The attackers push a minor update that introduces an unobtrusive background service worker with permissions to monitor storage state changes.
- OAuth Token Siphoning: When the victim logs into an enterprise platform (such as GitHub Enterprise or AWS SSO), the extension's background worker monitors network headers. It copies short-lived bearer tokens (Authorization: Bearer headers) or reads secure session cookies directly from the browser's cookie jar.
- Exfiltration via Covert DNS / Webhook: Because Manifest V3 blocks remote code execution but allows outbound telemetry to approved endpoints, the stolen tokens are encrypted and transmitted to the attacker's command-and-control server in real time.
| Attack Component | Traditional Manifest V2 Exploit | 2026 Manifest V3 Session Hijack |
|---|---|---|
| Payload Delivery | Remote eval() scripts injected from cloud CDN |
Pre-compiled Service Worker with legitimate storage APIs |
| Target Asset | Ad-injection, keystroke logging, redirect malware | Active OAuth 2.0 Bearer Tokens & Session Cookies |
| MFA Bypass Capability | Limited (Requires active credential phishing) | 100% Bypass (Steals already-authenticated sessions) |
| Detection Difficulty | Moderate (Flagged by antivirus network heuristics) | Extremely High (Uses native browser API calls) |
2. Step-by-Step Browser Audit: Inspecting Extension Permissions
To determine if any of your installed extensions hold excessive permissions that allow session eavesdropping:
Step A: Inspect Extension Storage Permissions
Open Google Chrome, Brave, or Microsoft Edge and navigate to chrome://extensions. Enable Developer Mode in the top-right corner, then inspect each extension's background inspector:
Join NextByte Tech Community on Telegram
Get immediate notifications for new verified Windows fixes, open-source utilities, and tech tutorials.
- Look for extensions requesting "Read and change all your data on all websites". If a simple calculator or dark mode utility requests access to all web domains, remove it immediately.
- Inspect the "Service Worker" inspect link. In the DevTools console, query active cookies:
chrome.cookies.getAll({}, console.log). If third-party utilities can access authentication tokens, revoke access.
Step B: Restrict Extension Site Access to "On Click"
Never allow third-party extensions to run persistently across every tab. Change permissions to on-demand execution:
- Right-click the extension icon in your browser toolbar.
- Hover over "This Can Read and Change Site Data".
- Change the setting from "On All Sites" to "When You Click the Extension".
This single tweak prevents background workers from silently listening to your authentication headers during banking or cloud console sessions.
3. Enterprise Hardening: Token Binding & DPoP (Demonstrating Proof-of-Possession)
For DevOps engineers and enterprise administrators, defending against token theft requires shifting to cryptographic proof protocols:
- Implement DPoP (RFC 9449): Configure your identity provider (Okta, Entra ID, Auth0) to enforce Demonstrating Proof-of-Possession. DPoP cryptographically binds OAuth tokens to a private key generated on the client machine. Even if a rogue extension siphons the raw bearer token, it cannot replay the token on another device without the private key.
- Shorten Access Token Lifespans: Reduce standard JWT bearer token expiration from 60 minutes to 5 minutes, forcing frequent cryptographic refresh handshakes.
- Device-Bound Passkeys: Enforce FIDO2 WebAuthn authentication prompts for high-privilege administrative actions (such as generating API keys or modifying IAM roles).
4. Summary Action Plan
Browser extensions remain the softest underbelly of modern desktop computing. Perform a quarterly extension audit, purge unmaintained plugins, enforce on-click execution, and isolate sensitive financial and cloud administration workflows in a dedicated, extension-free browser profile.