Chrome’s New Extension Rules: A Privacy Cleanup With a Hard Deadline
Google’s new Chrome extension privacy rules are stricter policies for the Chrome Web Store that limit data collection to what an extension genuinely needs, demand clear disclosure of all captured information, and threaten removal for any extension that silently expands tracking or abuses user trust. This is not a gentle nudge; it is a reset of the power balance between users, developers, and the browser. Google has given developers until August 1 to bring their extensions into line or face the extension removal deadline from the store. Extensions that gather data unrelated to their stated purpose will be treated as policy violators, and changing data practices after installation without notifying users is no longer tolerated. The message is clear: if an extension behaves like spyware, it no longer belongs in Chrome.
The timing of this crackdown is not accidental. Chrome 150 has started rolling out and removes the last practical workaround that let unsupported Manifest V2 extensions continue to run. Google has argued that retiring Manifest V2 reduces security risks and tech debt, but it is also an opportunity to tighten privacy expectations across the entire ecosystem. In recent months, we have seen free VPN extensions quietly start reading clipboard contents, including passwords and cryptocurrency wallet addresses, long after installation, while still claiming not to collect user data. Fake tools posing as note-taking or wallpaper add-ons have manipulated copied wallet addresses or tracked users in the background. Against that backdrop, a one‑month window to clean up or disappear feels less like a heavy hand and more like overdue maintenance on a browser that millions rely on daily.
Manifest V3: A Safer Framework That Still Leaves Open Doors
Google’s bet is that Manifest V3 security will raise the floor for all Chrome extensions, but the current transition shows that design alone cannot close every gap. Chrome 150’s removal of Manifest V2 workarounds is supposed to move developers to a safer platform, yet attackers have already adapted by abusing Manifest V3’s legitimate APIs rather than breaking them. That matters because it shifts the conversation: we are not dealing with obvious exploits, but with extensions that look technically compliant while being morally rotten. In other words, Manifest V3 is a better lock, but the system still needs guards at the door and clear rules about what guests can do once inside.
Microsoft’s Defender Security Research team uncovered a malicious Chromium extension named “Search for perplexity ai” that impersonated the popular AI search service via a typosquatted domain and intercepted user searches. Quote-worthy here is Microsoft’s finding that the extension relied heavily on Manifest V3’s Declarative Net Request APIs to create a “two‑hop” workflow: traffic first hit attacker infrastructure, then was redirected to legitimate providers. That workflow turned the address bar into a live wire. By overriding search suggestions, every character typed could be sent to attacker servers before users even pressed Enter, logging queries, headers, browser details, and IP addresses. No obvious breakage, no visible warning—just a silent data siphon using the same tools that power content filters and ad blockers.
Malicious Browser Extensions Exploit Trust, Not Just Code
The Perplexity hijacker proves a hard truth: malicious browser extensions thrive less on technical loopholes and more on the quiet exploitation of user trust. The extension did not attack Manifest V3; it misused allowed capabilities to route searches through attacker‑controlled servers and collect a rich stream of behavioral data, all while showing legitimate results from Perplexity, Google, or Bing. This kind of design is intentionally subtle. Victims saw the pages they expected, so almost no one would suspect that every keystroke in the address bar was being recorded. The same pattern shows up in supposed VPN tools that begin reading clipboards, fake note extensions that rewrite cryptocurrency wallet addresses, and wallpaper packs that quietly track users while claiming zero data collection.
For users, the practical impact is sharper than many realize. When an extension can transmit every character you type before you confirm a search, it can watch you think out loud, capturing half‑formed ideas, sensitive queries, and account details. Combine that with browser metadata and IP addresses, and attackers gain a detailed profile without needing to compromise the operating system. This is why Google’s renewed focus on Chrome extension privacy rules is welcome but also incomplete. Policies that demand minimal data collection and clear disclosure raise the bar, yet they assume users will read privacy notes and that developers are honest. History shows that bad actors are happy to look compliant while planning their next stealthy update.
Beyond Privacy: Jailbreak Tools, Prediction Markets, and AI Safeguards
Google is widening the net beyond tracking to tackle a new generation of risky services. Extensions that let users bypass safety restrictions on AI platforms—effectively jailbreak tools that aim to defeat content filters or usage limits—are being banned outright. At the same time, the company is extending its rules on regulated goods and services to block extensions that enable real‑money wagering based on prediction market outcomes. These moves are less about classic malware and more about curbing tools that normalize rule‑breaking and turn Chrome into a conduit for high‑risk behavior. With AI systems and betting platforms both under intense scrutiny, letting small extensions erode safeguards would be an obvious weak point.
These bans sit alongside stricter expectations for AI‑related extensions that remain allowed. Tools that help users interact with models must respect the platforms’ own protections instead of working around them. When paired with the privacy clampdown, this marks a philosophical shift: Chrome is not just a neutral window onto the web but a gatekeeper deciding which types of tools are acceptable. That will frustrate some developers, especially those who saw AI jailbreak helpers and prediction market widgets as creative innovation. Yet given how quickly these services can cause harm, drawing firmer lines is defensible. The real test will be whether enforcement is consistent, or whether clever rebranding lets the same behavior sneak back under a different name.
What Developers and Users Should Do Before August 1
With the extension removal deadline looming, both developers and users need to treat August 1 as more than an administrative date on a policy blog. Developers who hope to stay in the Chrome Web Store should strip out data collection that is not strictly necessary, update manifests and privacy disclosures to reflect every type of information they collect, and build mechanisms to inform users whenever practices change after installation. Extensions that were designed around broad permissions or speculative “future features” have to be rethought or risk disappearing. Those who cling to Manifest V2 or rely on opaque behavior will find Chrome 150 and the new rules to be a hard wall rather than a speed bump.
Users, meanwhile, should treat the crackdown as an opportunity to audit their own setups. Remove extensions you no longer use, scrutinize anything with access to your browsing history, clipboard, or search settings, and be suspicious of tools that mimic popular brands on slightly altered domains. Minimal permissions and clear privacy statements are not guarantees of safety, but they are a better starting point than flashy marketing or vague claims of “no data collected.” The Perplexity hijacker and the wave of clipboard‑reading VPNs are warnings that the extension ecosystem will always attract predators. The combination of Manifest V3 security and tighter privacy rules is a step forward; whether it becomes a true turning point depends on how actively developers comply and how carefully users choose what lives inside their browser.
