Why Browser Extensions Are a Quiet Security Risk
A friend asked me to look at her laptop because search results had started redirecting to a site she had never heard of. No malware alert, no sketchy download, nothing in her installed programs.

A friend asked me to look at her laptop because search results had started redirecting to a site she had never heard of. No malware alert, no sketchy download, nothing in her installed programs. The cause was a coupon finder extension she had added two years earlier and completely forgotten. It still worked. It still found coupons. It had also been sold to a new owner at some point and had quietly started rewriting her search traffic.
That pattern is the part of browser security almost nobody checks. People update their operating system, pick a decent password manager, and then leave eleven extensions sitting in the toolbar with permission to read every page they open. An extension with full site access can see what you type into a banking form the same way it can see a coupon code, and the browser will not warn you again after the day you installed it.
What you actually agreed to on install day
The permission dialog is the whole story, and it goes past in a second. The line that matters most is the one that says the extension can read and change all your data on all websites. That is not a warning about a theoretical risk. It is a literal description of the capability: the extension's code runs inside every page you load, with access to the page content, the form fields, and the cookies that keep you signed in.
Some extensions genuinely need it. An ad blocker has to inspect pages. A grammar checker has to read the text you type. A password manager has to see login forms, which is exactly why the choice of manager deserves real thought, and the notes on picking a password manager you will keep using go into which ones limit their own access.
Most extensions do not need it. A color picker, a screenshot tool, a tab organizer, a dark mode toggle. Those can run on the page you are looking at when you click them, and nothing else. Browsers have supported that narrower setting for years, and hardly anyone changes it, because the install flow never mentions it exists.
Why the star rating advice is backwards
The standard guidance is to stick to extensions with a high rating and a large install count. I understand the instinct. I think it is close to useless, and in one specific way it points you at the wrong thing.
Popularity is the asset. An extension with 400,000 users is worth money to someone who wants an injection point, and there is a small industry of people who approach extension developers with an offer. The developer sells, the new owner pushes an update, and every one of those 400,000 browsers installs it automatically overnight. The rating stays high because the reviews were written about the old version. The install count stays high because nobody noticed.
Rating also measures whether an extension does its job pleasantly, which has nothing to do with what it can see. I have never read a one star review that said the permissions were too broad.
What I look at instead: the last update date, whether the developer has a real identity and a changelog, and whether the permission list matches the described function. An extension that calls itself a unit converter and asks to read all your data is telling you something useful before you install it.
The twenty minute audit
Do this once and then once a year. It takes longer the first time because of what you find.
- Open your extensions page. In Chrome and Edge it is under the puzzle piece icon, then Manage. In Firefox it is the menu, then Add-ons. Count how many you have. Most people I have done this with sit between 8 and 15 and can name about 4.
- Remove anything you cannot remember installing or have not knowingly used in three months. Not disable. Remove. A disabled extension still sits in your profile and can come back with a sync.
- For each survivor, open its details and find the site access setting. Change it from on all sites to on click wherever the extension still works that way. Screenshot tools, pickers and converters all survive this fine.
- Read the permission list on the ones you keep at full access. If you cannot explain in one sentence why a password field reader needs to be in your browser, that is your answer.
- Check the developer and the last update. An extension last updated four years ago is not maintained, and an unmaintained extension with full page access is a liability even if the original author was honest.
- Turn off extension sync if you use the same account on a work machine and a personal one. It is the quickest way for something you removed in one place to reappear in another.
Step three is the one that does the most work for the least effort. Step one is the one that tends to shock people.
Signs an extension has turned
You will usually notice behavior before you notice a setting. The symptoms my friend had are typical: search results that land somewhere unexpected, a new default search engine, prices or links appearing on shopping pages that the site did not put there, or a browser that suddenly takes four seconds to open a tab.
Two checks tell you most of it. First, open a page you know well and look for anything inserted that should not be there. Second, open your browser's network or performance panel with a single plain page loaded, something local like a page served from localhost or your own saved HTML file, and see whether requests are going out to domains you do not recognize. A clean local page should talk to almost nothing.
If you do find one, remove it and then change the passwords for anything sensitive you signed into while it was installed. An extension with full page access could have read a session cookie, and a password change invalidates old sessions. The security section has the order to do that in, starting with email.
The quieter cost: identifiability
Separate from the hijacking risk, there is a tracking side effect people rarely connect. The set of extensions you run can be detectable from a web page, because some of them inject visible changes into the page or expose files that a script can probe. A reasonably unusual combination of five or six extensions makes your browser easier to pick out of a crowd, even with cookies cleared.
That matters more if you care about not being followed around than if you only care about account safety. It is the same mechanism described in the piece on browser fingerprinting, and it is another argument for keeping the list short rather than keeping it tidy.
My own count is four, and one of those is on click only. That is not discipline. It is the result of one afternoon spent cleaning up somebody else's laptop and deciding I did not want the same afternoon myself.
FAQ
Are extensions from the official store safe?
Store review catches obvious malicious code, but it cannot tell whether an extension will change hands next year or what a future update will do. Treat store presence as a minimum, not as a guarantee.
Does a VPN protect me from a bad extension?
No, and this is worth stating plainly. A VPN protects traffic in transit. An extension runs inside your browser, where the page is already decrypted, so it reads the content before any tunnel is involved.
Is on click access annoying to use?
Less than you expect. You click the extension icon on the page where you want it, which is roughly what you were doing anyway. The ones where it genuinely hurts are ad blockers and password managers, so leave those on all sites.
What about extensions in a private window?
They are off by default and you have to allow each one. Any extension you have allowed in private windows has exactly the same access there, which defeats part of the point of using one.
More in Security
Security
How to Check Which Devices Are Signed Into Your Accounts
I checked my own Google account in February expecting a tidy list of four devices. It showed nine.
Security
Why Account Recovery Is the Weak Spot in Your Security
You can use a 20 character password, a passkey and an authenticator app, and still lose an account in four minutes.
Security
How to Check If Your Email Was in a Data Breach
You got an email saying a company you barely remember "experienced a security incident," and now you are wondering if your...