Stay up to date with AI tools, model releases, and developer workflows that matter.
It has been revealed that weekly. Free. One click to leave.
In a recent development, 7 Day Free Trial. Cancel Anytime.
The extension a developer installed three years ago can probably read everything they do in the browser today.
Industry observers note that general online security advice from VPNpro and similar guides cover the network side of staying safe, but they cannot see what an extension does inside the browser. That layer is more the developer's responsibility. The risk is complicated, but the fix is simple: request fewer permissions, narrower host access, and less data, and review every update. Here is a walkthrough of each.
According to recent reports, think about what a developer has open on a normal day: a cloud console, a staging dashboard, a private repo, maybe webmail. One over-permissioned extension sees all of it.
A 2025 USENIX Security study of 21 extension developers found that developers often recognize the privacy and security risks their extensions pose, but frequently lack the knowledge and resources to deal with them. That matches what many privacy problems look like in practice: not a malicious author, but a well-meaning developer shipping software with settings nobody reviewed.
In a recent development, the most common mistake is asking for broad access early and planning to trim it later. Later rarely arrives.
A manifest like this should raise eyebrows:.
A developer who cannot justify a permission in a short sentence likely shouldn't include the permission in the build.
Host permissions deserve their own attention because they define how far the extension can reach. A few habits make a real difference:.
This also helps adoption. People hesitate when an extension asks to read every site they visit. A narrow request looks, and is, more trustworthy.
Recent findings suggest that analytics and error logging are where good intentions leak. A crash report that includes the full page URL may contain a session token in the query string. A “usage event” may capture page titles from internal tools.
The most secure approach is to collect only the data a feature needs and to process the data locally if possible. When data has to be sent, it should be stripped down to the absolute minimum. Avoid sending query strings, and truncate URLs to the domain name where possible. Never send page content if it is not absolutely necessary.
It has been revealed that remote code is another trap. Manifest V3 restricts remotely hosted code for a good reason. A script fetched at runtime can modify its behavior after the fact, and one can’t audit what it will do in the future. Bundle everything and the code that is reviewed will be identical to the code that is run.
A good extension today can become a risky one next year. Two patterns keep repeating.
Ownership changes. Popular extensions get sold, and the new owner ships an update with tracking or worse. The Great Suspender, a widely used tab tool, ended up flagged as malware after a change of hands.
Compromised publisher accounts. If an attacker phishes the developer account, they can push a malicious update to every existing user. Cyberhaven’s extension was hit by a phished administrator account in late December 2024.
The defenses are mostly boring, which is a good sign. Hardware-key two-factor authentication on the publisher account, a short list of people allowed to publish, and a review step before each release stops most of it. Lockfiles, pinned versions and regular dependency audits cover the code side.
Teams that only install extensions can apply the same thinking. Keep an approved list, review updates that change permissions, and remove anything nobody uses. Following security news is worthwhile too, since incidents involving popular extensions tend to be reported publicly.
Extension privacy does not stop at the manifest. Developers often test on café Wi-Fi or shared networks, with debug builds that log far more than production ever would. Network-level protection is one sensible layer for that, and readers who want background on it can find general guides covering encryption, VPNs and safer browsing habits.
It is only one layer, though. A VPN protects traffic in transit. It does nothing about an add-on that reads page content inside the browser, so it never replaces a proper permission review.
It has been revealed that simpler habits do more here. A separate browser profile for development keeps test extensions away from personal accounts. Fake or low-privilege accounts for testing avoid exposing real credentials. And installers for any tool, VPN clients included, should come from the official site or store, never from a mirror.
Industry observers note that safe extensions come down to restraint. Ask for less access, collect less data, send less off the device, and explain more to the user. Developers who treat every permission as a liability end up with extensions people can trust, and teams that review what they install avoid the worst surprises.
It has been revealed that 7 Day Free Trial. Cancel Anytime.
