Is Popup Blocker Pro safe?
Popup Blocker Pro is high risk. Every navigation, Popup Blocker Pro sends the visited URL, referrer, and a persistent install ID to data.popup-blocker.org. 3 POSTs were captured with URL, referrer, ID, timestamps, firing on every navigation, every site, no consent prompt.…
Popup Blocker Pro findings
Browsing History Transmitted to data.popup-blocker.org on Every Navigation
Every navigation, Popup Blocker Pro sends the visited URL, referrer, and a persistent install ID to data.popup-blocker.org. 3 POSTs were captured with URL, referrer, ID, timestamps, firing on every navigation, every site, no consent prompt.
What actually happens
You navigate to any web page in any tab.
The extension sends the full URL, the URL you came from, and a persistent identifier tied to your install to data.popup-blocker.org.
This happens on every main-frame navigation, every site, every tab, without any user action beyond normal browsing.
Captured request
Our dynamic analysis captured 3 POST requests to this endpoint. Browsing history was transmitted on every main_frame navigation.
- Content-Type
- application/json;charset=utf-8
{ "fileDate": "2026-04-14T10:23:41.112Z", "deviceTimestamp": 1744626221112, "userId": "fe0916f3-1ff9-4931-b5ae-7ed70956b98f", "referrerUrl": "https://www.google.com/", "targetUrl": "https://www.google.com/account/about/", "requestType": "GET", "userIdSync": "fe0916f3-1ff9-4931-b5ae-7ed70956b98f"}What Popup Blocker Pro sends on every page you visit
- The URL you visitedhttps://www.google.com/account/about/
The exact page address you navigated to, including any query parameters.
- The URL you came fromhttps://www.google.com/
Where you were before this page, either the referring URL or the tab's initiator origin.
- Your persistent user IDfe0916f3-1ff9-4931-b5ae-7ed70956b98f
A UUID generated once when you install the extension and stored permanently. It links all your page visits together across sessions.
- Your synced user IDfe0916f3-1ff9-4931-b5ae-7ed70956b98f
A second UUID also stored in Chrome's sync storage, survives reinstalls if you're signed into Chrome.
- HTTP methodGET
Whether the page load was a GET or POST request.
- Device timestamp1744626221112
The exact time on your device when the navigation completed, to the millisecond.
- ISO timestamp2026-04-14T10:23:41.112Z
The same moment expressed as an ISO 8601 date-time string.
The code that does this
The navigation listener and payload sender from the extension's shipping source (sw.js):
Registers a listener on every completed top-level navigation
// Fires for every completed main-frame request across ALL URLs.// There is no allowlist — every site triggers the handler.chrome.webRequest.onCompleted.addListener(sendBrowsingHistory, { urls: ['<all_urls>'], types: ['main_frame']});Collects URL + referrer + two persistent UUIDs and POSTs them
// Called on every page navigation.async function sendBrowsingHistory(requestDetails) { const localUUID = await localStore.get('uuid'); // persistent, device-local UUID const syncedUUID = await syncStore.get('uuid'); // same UUID in Chrome sync storage const refMap = await localStore.get('stats_refs') || {}; await postToServer({ fileDate: new Date().toISOString(), // ISO timestamp deviceTimestamp: Date.now(), // ms since epoch userId: localUUID, // identifies this browser install referrerUrl: refMap[requestDetails.tabId] || requestDetails.initiator, targetUrl: requestDetails.url, // the page you just loaded requestType: requestDetails.method, // 'GET' userIdSync: syncedUUID }); // Update refMap so the next navigation on this tab gets this URL as its referrer. refMap[requestDetails.tabId] = requestDetails.url; chrome.storage.local.set({ stats_refs: refMap });}Where your browsing history is sent
- data.popup-blocker.org
Receives a POST containing the visited URL, referrer URL, and persistent UUID on every main-frame navigation. Operated by the Popup Blocker Pro developer.
Blocking Rules Fetched from Remote Server and Updated Every 60 Seconds
Every 60 seconds, it fetches api.popup-blocker.org/settings for a whitelist (skips popup blocking) and blacklist (scripts blocked), applied at once, overriding local settings.
The server adds/removes domains freely; 5 GETs seen.
What actually happens
Every 60 seconds, the extension contacts api.popup-blocker.org/settings.
This starts immediately on extension startup and repeats indefinitely.
The server returns whitelist/blacklist arrays, applied immediately: whitelisted domains skip popup blocking; blacklisted domains get scripts blocked via declarativeNetRequest.
If the server returns different lists on the next poll, the extension updates its blocking rules accordingly, no user interaction needed.
Captured request
Our dynamic analysis observed 5 GET requests to this endpoint at approximately 60-second intervals. The extension's storage showed pb_defaultWhitelist and pb_defaultBlacklist being populated with server-provided data after each response.
- Extension
- kiodaajmphnkcajieajajinghpejdjai
- X-Requested-With
- XMLHtpRequest
- Extension-Version
- 2.0.5
What's stored on your device
After each fetch, the extension stores the whitelist/blacklist locally, controlling which domains skip blocking or get scripts blocked.
- Location
- chrome.storage.local keys 'pb_defaultWhitelist' and 'pb_defaultBlacklist'
{ "pb_defaultBlacklist": [ "competitor-adnetwork.com", "unwanted-tracker.net" ], "pb_defaultWhitelist": [ "example-partner.com", "sponsored-site.com" ]}The code that does this
The remote configuration fetch and application logic (sw.js):
Polls remote server every 60 seconds for updated blocking rules
// Runs immediately on startup and then every 60 seconds.async function updateSettings() { const response = await fetch('https://api.popup-blocker.org/settings', { headers: { 'Extension': extensionId, // identifies this extension to server 'Extension-Version': extensionVersion, 'X-Requested-With': 'XMLHtpRequest', // note: typo in source ('XMLHtpRequest') } }).then(r => r.json()); // If the server returned new lists, overwrite local copies immediately. if (response.data.whitelist) { await chrome.storage.local.set({ pb_defaultWhitelist: response.data.whitelist, // domains exempt from popup blocking pb_defaultBlacklist: response.data.blacklist // domains whose scripts get blocked }); } // Apply the new blacklist as a live DNR rule. await applyBlacklistRule(); // Schedule the next poll. setTimeout(updateSettings, 60_000);}Applies blacklisted domains as a Chrome declarativeNetRequest script-blocking rule
// Replaces rule ID 1 with a block rule for all domains in the server-controlled blacklist.async function applyBlacklistRule() { const blacklist = await localStore.get('pb_defaultBlacklist'); chrome.declarativeNetRequest.updateDynamicRules({ removeRuleIds: [1], addRules: [{ id: 1, priority: 1, action: { type: 'block' }, condition: { requestMethods: ['get'], requestDomains: blacklist, // ← list comes entirely from the remote server domainType: 'thirdParty', resourceTypes: ['script'], } }] });}Remote configuration server
- api.popup-blocker.org
Provides whitelist/blacklist arrays every 60 seconds, controlling which domains skip popup blocking and which have scripts blocked. Operated by the Popup Blocker Pro developer.
Each Blocked Popup Reports Your Page and Target URL to data.popup-blocker.org
Every blocked popup sends telemetry to a developer server: page hostname, popup target URL, a persistent install identifier, and block reason.
This links reports to the same install, letting the developer track blocked-popup sites.
What actually happens
You visit any website where a popup or window.open() call is attempted.
Blocks the popup and POSTs telemetry to data.popup-blocker.org/events/block: page hostname, popup target URL, and a persistent install identifier.
This fires on every blocked popup across all websites. No opt-out is offered and no consent prompt is shown.
Captured request
Two POST requests to this endpoint were observed during dynamic analysis. The server responded with HTTP 200. The body above reflects the fields confirmed in the captured traffic; the on-wire payload also carries target_host, target_etld1, page_etld1, is_top_frame, anchor_target, anchor_rel, and locale per source analysis.
- Content-Type
- application/json
{ "device_ts": 1782622104469, "reason": "window_open", "target_url": "https://www.google.com/", "page_host": "www.example.com", "install_id": "bd896383-d1ac-4b71-bb67-101e1801eeb0", "ext_version": "3.0.6"}What each blocked-popup report contains
- Your persistent install IDbd896383-d1ac-4b71-bb67-101e1801eeb0
A UUID generated on first run and stored permanently, linking every blocked-popup report across sites and sessions to the same install.
- The page you were onwww.example.com
The hostname of the site you were browsing when the popup was blocked, indicates which sites in your history generate popup attempts.
- The popup's target URLhttps://www.google.com/
The full URL the popup was trying to open, including any path and query parameters.
- Block reasonwindow_open
How the popup was triggered, by a script calling window.open(), an anchor link, or a form submission.
- Timestamp1782622104469
The exact millisecond on your device when the popup was blocked.
- Extension version3.0.6
The version of Popup Blocker Pro installed in your browser at the time of the event.
The code that does this
Payload assembly and transmission from the extension's shipping source:
Content script: assembles blocked-popup context and relays to service worker
// Fires in the content script whenever a popup is blocked.// Collects page context and the blocked popup's target, then relays to service worker.function reportBlockEvent(blockedArgs, reason, isTopFrame) { const targetUrl = resolveUrl(blockedArgs[0]); const payload = { device_ts: Date.now(), // ms timestamp of the block event reason: reason, // 'window_open' | 'anchor' | 'form' target_url: targetUrl, // full URL the popup was trying to open target_host: safeHost(targetUrl), // hostname of popup destination target_etld1: getDomain(targetUrl), // eTLD+1 of popup destination page_host: window.location.host, // hostname of the page you are on page_etld1: getDomain(window.location.href), // eTLD+1 of your page is_top_frame: isTopFrame, // whether blocked in the top frame anchor_target: String(blockedArgs[1] || ''), anchor_rel: reason !== 'window_open' ? String(blockedArgs[2] || '') : '', locale: chrome.i18n.getUILanguage(), // browser UI locale }; // Pass to service worker, which appends install_id before sending. chrome.runtime.sendMessage({ name: 'reportBlock', payload });}Service worker: appends install ID and sends to data.popup-blocker.org
// Fires in the service worker on every 'reportBlock' message.// Appends the persistent install ID and transmits to the developer's server.async function reportBlockEvent(payload) { const installId = await getInstallId(); // UUID from chrome.storage.local, created once at install await fetch('https://data.popup-blocker.org/events/block', { method: 'POST', keepalive: true, // request survives page navigation headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ ...payload, install_id: installId, // persistent cross-site identifier ext_version: chrome.runtime.getManifest().version, }), });}Where blocked-popup telemetry is sent
- data.popup-blocker.org
Receives a POST on every blocked popup: page hostname, popup target URL, block reason, timestamp, and a persistent install UUID. Operated by the Popup Blocker Pro developer.
+2 more findings not shown
If you have Popup Blocker Pro installed
- Open
chrome://extensionsand turn on Developer mode to show IDs. Find the one with IDkiodaajmphnkcajieajajinghpejdjaiand choose Remove. - Block the servers only it was seen contacting:
api.popup-blocker.org,data.popup-blocker.org. - Scan your browser to check the rest of your extensions.
What Popup Blocker Pro can do
Permissions this extension asks for, as declared in version 2.0.5. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to. The current listed version is 3.0.6, which we have not unpacked yet.
Read and change your data on every site you visit
*://*/*
Store data in your browser
storage
Watch every request your browser makes
webRequest
Block and redirect the requests your browser makes
declarativeNetRequest
See the address and title of every tab you have open
tabs
Add items to the right-click menu
contextMenus
Popup Blocker Pro version history
2.0.5
Mar 4, 2026
3.0.2
May 10, 2026
Where Popup Blocker Pro sends data
- api.popup-blocker.org/settings6 calls
From its background script · only this extension
- data.popup-blocker.org/process6 calls
From its background script · only this extension
- www.google-analytics.com/collect4 calls
From its background script · 238 other extensions
- api.popup-blocker.org/white-list/create3 calls
From its background script · only this extension
- api.popup-blocker.org/popup-banner2 calls
From its own pages · only this extension
- data.popup-blocker.org/events/block2 calls
From its background script · only this extension
- www.google.com/s2/favicons2 calls
From its own pages · 108 other extensions
- t2.gstatic.com/faviconV21 call
From its own pages · 34 other extensions
Chrome Web Store listing
- Versions
- 3.0.2 latest of 2 seen since March 4, 2026
- Store rating
- 4.3 from 7,755 ratings
- Last updated
- May 15, 2026
- Size
- 252 KiB
- Privacy policy
- popup-blocker.org
