Is Popup Blocker (strict) safe?
Popup Blocker (strict) intercepts and blocks popup and tab-open requests on every page, presenting a confirmation UI that any page script can inject fake entries into.
The extension injects a content script on all URLs that captures window.open and tab-creation calls before they execute, then renders a confirmation iframe asking the user whether to allow, deny, or redirect each popup. The confirmation iframe registers a postMessage listener with no origin check, meaning any page can send crafted requests into it and cause the UI to display attacker-controlled entries; if the user clicks Allow on one, the extension opens the attacker-supplied URL via chrome.tabs.create.
Part of this rating comes from analysis signals we haven't published as detailed findings yet.
Who publishes itJeremy Schomery - no other listings under this identity, 1 shared hostname
Jeremy Schomery - no other listings under this identity, 1 shared hostname
What this publisher told the store about itself, and the other listings that told it the same thing.
Shared hosts - 1 hostname
Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
What it can do
Permissions this extension asks for, as declared in version 0.9.3. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Read and change your data on every site you visit
<all_urls>
Store data in your browser
storage
Run its own code inside the pages you visit
scripting