Privacy & Security

How to Check If a Chrome Extension Is Safe Before You Install It

A practical 10-minute check for any Chrome, Edge or Brave extension: publisher, permissions, update history, ownership changes and the red flags that matter in 2026.

Most extensions are fine. The problem is that a dangerous one looks exactly the same as a good one in the store: a nice icon, a few thousand users, a 4.5-star rating. Malicious extensions in 2026 rarely look like malware. They look like a screenshot tool, a color picker or an “AI assistant” that was useful last month, and then an update changes what it does.

This is a practical check to run before installing any extension, built around what the Chrome Web Store actually shows you. It takes about ten minutes the first time and two minutes once you know where to look. Everything below works in Chrome, and almost all of it applies to Edge and Brave too, since they install from the same store.

Why “it’s in the official store” is not enough

Google reviews every extension and every update, and that review catches a lot. But three things get through often enough that you should plan for them:

  1. Ownership transfers. Extensions are bought and sold. A buyer gets the existing user base and can push an update to every one of those browsers. In March 2026, researchers documented two Chrome extensions, QuickLens and ShotBird, that turned malicious after changing hands. One of them had carried Google’s old “Featured” badge. The new code stripped security headers from pages and loaded JavaScript from a remote server at runtime, so the harmful part never appeared in the files Google reviewed (The Hacker News report).
  2. Data harvesting inside a “useful” product. Some extensions do exactly what they promise and also collect your browsing or AI-chat data on the side. Researchers reported free VPN and ad-blocking extensions that scraped conversations from ChatGPT, Claude, Gemini, Copilot and other chatbots.
  3. Affiliate and search hijacking. Extensions that quietly rewrite shopping links or change your search engine make money for their owners with every click you make.

So the question isn’t “is it in the store?” It’s “who controls this code, what can it touch, and would you notice if it changed?”

Step 1: Ask whether you need an extension at all

Every extension you install is code that updates without asking you. The safest extension is the one you don’t install. Before searching the store, check whether the browser already does it:

  • Tab clutter: Chrome now has tab groups, saved groups, Split View and (since Chrome 147 in April 2026) vertical tabs. See our guide to Chrome’s built-in tab tools.
  • Screenshots: Chrome DevTools can capture full-page screenshots (open DevTools, press Ctrl+Shift+P, type “screenshot”).
  • Passwords: Google Password Manager is built in. Our password manager comparison covers when a dedicated one is better.
  • Reading mode, translation, PDF viewing: all built in.

If the browser covers 80% of what you need, the remaining 20% is rarely worth giving a stranger access to your pages.

Step 2: Read the listing like an investigator

Open the extension’s page in the Chrome Web Store and scroll past the screenshots. You’re looking for these details:

Where What to check Good sign Red flag
Publisher name and badge Who publishes it, and is there an Established publisher badge? A company or developer you can find elsewhere, with a website and history A random Gmail address, a brand-new domain, or a name that imitates a famous brand
“Updated” date and version When it last changed Regular but not hyperactive updates Dormant for years, then a sudden update; or a new owner plus an update
Users and reviews Recent reviews (sort by newest) Reviews describe actual features Recent reviews mention ads, redirects, “it changed”, or new pop-ups
Privacy practices tab What data the developer declares collecting Little or nothing, matching the purpose A tab-counter that collects “web history” and “personal communications”
Developer website / privacy policy Do the links work? Real site, clear policy No site, a parked domain, or a policy copied from somewhere else

Two notes on badges, as of November 2026. The Established publisher badge means Google verified the publisher’s identity and the account has a good track record. It’s a useful signal. The Featured badge is being retired: Google announced in August 2026 that it’s sunsetting the program and will rely on a refreshed rating system that weighs recent reviews more heavily (Chrome for Developers announcement). Either way, a badge describes the past, not what the next update will do.

Step 3: Compare permissions with the purpose

When you click Add to Chrome, a dialog lists what the extension can do. This is the most important screen in the process and the one most people skip. The question is simple: does every permission make sense for what this extension says it does?

  • A dark-mode extension that needs “Read and change all your data on all websites” is plausible, since it restyles every page.
  • A calculator or timer that needs the same permission is not.
  • A coupon finder that wants “Read your browsing history” is telling you its business model.

Our permissions guide translates each warning into plain English. If you’re unsure, don’t install. You can always come back later.

Step 4: Check the developer’s other extensions

Click the publisher name. A developer with one focused product and a real website is a different risk from an account with forty near-identical “AI chat” extensions published in the same month. Watch for clusters of copycat tools with slightly different names. That pattern was common in 2026 among extensions caught harvesting AI conversations.

Step 5: Look for ownership changes

This is harder, because the store doesn’t show a history of owners. Some practical clues:

  • The publisher name or contact email on the listing doesn’t match the name in older reviews or on the original website.
  • The extension’s GitHub repository (if it had one) has been archived, or its README says the project was sold.
  • The privacy policy now lives on a different domain from the developer’s site.
  • Long-time users mention in recent reviews that “the new update added…” something unrelated.

If an extension you rely on changes hands, treat it like a new install and run this whole check again.

Step 6: Install with the smallest possible access

After installing, open chrome://extensions, click Details on the extension and find Site access. You usually get three choices:

  • On click: the extension can only read the current page after you click its icon.
  • On specific sites: only on sites you list.
  • On all sites: everywhere, all the time.

For anything that doesn’t need to run everywhere, choose On click or a short list of sites. A grammar checker might need all sites. A tool you use on one web app doesn’t.

While you’re on that page, leave Allow in Incognito off unless you have a specific reason. Extensions don’t run in Incognito by default, and that’s a useful boundary.

Step 7: Keep checking after you install

Safety isn’t a one-time decision, because extensions update silently. A few habits keep you ahead:

  • Run Safety Check. In Chrome go to Settings → Privacy and security → Safety Check. It flags extensions that were removed from the store for malware or policy violations, and Chrome disables extensions removed for malware automatically.
  • Prune every few months. If you haven’t used an extension in a month, remove it. Fewer extensions means fewer people who can push code into your browser.
  • Watch for behavior changes. New pop-ups, a changed search engine, a new tab page you didn’t choose, or shopping links that redirect strangely are reasons to disable the extension first and investigate afterwards.
  • Use a separate profile for sensitive work. A Chrome profile with no extensions for banking and admin dashboards is cheap insurance. See profiles, Guest mode and Incognito explained.

A quick checklist you can reuse

Before installing:

  1. Does the browser already do this?
  2. Is the publisher identifiable, ideally with an Established publisher badge?
  3. Do the newest reviews sound normal?
  4. Does the privacy practices section match the purpose?
  5. Does every permission make sense?

After installing:

  1. Set Site access to the minimum.
  2. Keep Incognito access off.
  3. Run Safety Check and prune regularly.

What to do if you think an extension went bad

  1. Turn it off in chrome://extensions straight away. Removing it is better if you don’t need its stored data.
  2. Change passwords for important accounts you used while it was active, starting with email, and sign out of other sessions.
  3. Check your search engine and startup pages in Chrome settings, because hijackers often change them.
  4. Report it from the store listing using Report abuse (under the extension’s overflow menu or support section).
  5. On a work machine, tell your IT team. Browser extensions are a common way into company accounts.

None of this requires you to be paranoid. It requires you to treat extensions like the apps they are: software with access to everything you do in the browser, updated by someone you’ve probably never met.

Keep reading