The Quiet Permissions: An Afternoon Audit of the Browser Extensions You Forgot You Installed
Photo: browser extensions settings page displayed on a laptop screen, via cdn.neowin.com
Somewhere in your browser there is an extension you installed to solve a small problem in a single afternoon — a coupon finder, a screenshot tool, a PDF converter, a theme pack. The problem was solved years ago. The extension is still there, still updating, and still holding permissions that were granted with a single click and never revisited.
Extensions occupy an unusual position in personal security. They run inside the page, which means they are not always constrained by the boundaries that protect ordinary websites. An add-on with broad access can read the text of your banking portal, capture what you type into a form, modify the interface of a page to show something the site never intended, and observe your browsing history across every domain you visit. Many are well built and responsibly operated. The difficulty is that users have no efficient way to tell which are which.
What the Permission Labels Actually Mean
The wording is deliberately plain on the install screen and rarely read again. A handful of permissions carry most of the weight.
- Read and change all your data on all websites. Effectively full visibility into page content, from email to account balances. This is the permission that most extensions genuinely need and also the one that enables the most damage.
- Read and change your browsing history. Allows the add-on to see every site you visit and to alter that record.
- Read data you copy and paste. Access to clipboard contents, which routinely include passwords and card numbers.
- Modify data you copy and paste, or manage downloads. Capable of redirecting downloads to different files.
- Display notifications. Frequently abused for ad injection and unwanted redirects.
An extension asking for more than its stated purpose requires is an extension worth removing, regardless of how good its reviews are.
A Fifteen-Minute Walkthrough for Each Browser
Chrome and Edge. Open the extensions page — chrome://extensions in Chrome, edge://extensions in Edge. Turn on developer mode only if you intend to sideload, and otherwise leave it off. Review the list, and for each entry open the Details panel. The panel shows the exact permissions granted and, critically, the date of the last update.
Firefox. Navigate to about:addons and select the Extensions panel. Each entry offers a Permissions tab and a version history. Firefox displays the developer and the signing status, which is useful for confirming that the add-on still exists as a maintained project.
Safari. Extensions live in the Safari settings under the Extensions tab, and each one is toggled individually. Safari is more restrictive by default — extensions must be enabled per-site for some functions — but the list should still be reviewed rather than assumed.
As you work through the list, note three things for every extension: when it last received an update, who publishes it, and whether you can articulate what it does today. If any of those three answers is uncertain, the extension belongs in the removal pile.
Abandoned Add-Ons and the Ownership Problem
An extension that has not shipped an update in two or three years is not automatically malicious, but it is unmaintained. Unmaintained code accumulates known vulnerabilities, and its user base becomes an asset. A recurring pattern in the extension market involves a developer selling a popular add-on to a buyer who inherits its install base and then changes its behavior in a later update — introducing tracking, ad injection, or credential interception that existing users receive quietly.
Watch for a changing publisher name, a sudden shift in the privacy policy, a version jump accompanied by new permissions, or a wave of recent reviews describing redirects and pop-ups. Permission increases require your approval, but they are presented as an ordinary prompt that most people dismiss.
Removing, Then Replacing Carefully
Removal is the easy part; the removal button is on the Details panel in every browser covered here. Replacement deserves more thought. Prefer extensions published by the organization whose service they extend, and prefer those distributed through official browser stores rather than vendor websites offering standalone installers. Read the permission list before the description. Favor add-ons that request access only for specific sites — browsers now offer per-site access settings for exactly this reason.
A useful rule of thumb is to keep the list short. Every extension is a small ongoing trust decision, and five well-chosen add-ons produce less exposure than twenty accumulated ones. Where a built-in browser feature now covers the same ground — reading mode, screenshot capture, password management, tracking prevention — retire the third-party equivalent.
A Calendar Entry Instead of Good Intentions
Schedule a quarterly review of the extensions page alongside password updates and software patches. It takes minutes, requires no technical background, and restores a degree of control that most users assume they have already. The permissions you granted years ago are still active today, and the only person positioned to renegotiate them is you.