Is Ad Block Wonder safe?

High risk

Ad Block Wonder is high risk. Besides the rules reviewed in the Web Store, Ad Block Wonder fetches a larger set of 10,000 or more rules from the developer's server. Testing confirmed thousands of domains were applied, and they can change.…

Wonder Blockv6.0Extension ID fpkbnjejghdcncegfglnapabnljcimdcChrome Web Store
79Risk
Who publishes it

Wonder Block - no other listings under this identity, 7 shared hostnames

Publisher
Wonder Block

Shared hosts - 7 hostnames

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.

analyzer.fc2.com
Also called by 4 other listings, including SBlock
ish.tumedia.no
Also called by 4 other listings, including aBlock - Ads Blocker, SBlock
rranking3.ziyu.net
Also called by 4 other listings
s1.aspservice.jp
Also called by 4 other listings
ssl-wolterskluwer.met.vgwort.de
Also called by 4 other listings, including aBlock - Ads Blocker, SBlock
t.myvisualiq.net
Also called by 4 other listings, including aBlock - Ads Blocker, SBlock
ziyu.net
Also called by 4 other listings, including aBlock - Ads Blocker
AI-assisted analysis.

Ad Block Wonder findings

Downloads thousands of extra blocking rules from the developer's server

HighunwantedCWE-829Dynamic sandbox

Besides the rules reviewed in the Web Store, Ad Block Wonder fetches a larger set of 10,000 or more rules from the developer's server.

What actually happens

You did this

The developer's server sends the extension a URL and version number for a bulk rules file.

The extension did this

The extension downloads that file and loads thousands of domain-matching rules directly into Chrome's blocking engine.

The request for the rules file includes your extension's runtime ID as a URL parameter.

Captured request

GEThttps://wonderupdates.com/compiled_rules.php?extid=kejigfhcnfgbejgnacjpehlledjlgpbf

HTTP 200. This URL, including the runtime-ID query parameter, was observed being fetched by the service worker immediately after the extension's remote-config POST vended a matching rulesUrl/rulesVersion pair.

What the fetched rule set can do

  • Which file is downloaded
    https://wonderupdates.com/compiled_rules.php

    The address the rules are fetched from, determined by the server response, not fixed in the extension package.

  • Your extension's runtime ID
    ?extid=kejigfhcnfgbejgnacjpehlledjlgpbf

    Sent as a query parameter on every rules download, letting the server tell individual installs apart.

  • Rule scale
    4,709 domains in one rule; 5,000 in another in the same fetch

    A single downloaded rule set can name thousands of domains to redirect or block on your device, none reviewed by the Chrome Web Store.

The code that does this

Bulk rules fetch and install (src/background.js)

Readable version

Same logic, annotated

src/background.js
// rulesUrl came from the server's last config response, not the extension package.const fetchUrl = rulesUrl.includes("?")  ? `${rulesUrl}&extid=${encodeURIComponent(ch.runtime.id)}` // tags the download with your install ID  : `${rulesUrl}?extid=${encodeURIComponent(ch.runtime.id)}`;// Download whatever JSON array is at that URL, up to 60s.const response = await fetch(fetchUrl, { signal: controller.signal });if (!response.ok) return;const bulkRules = JSON.parse(await response.text());if (!Array.isArray(bulkRules)) return;// Swap out the previous server-fetched rule set for the new one, applied// directly to Chrome's declarativeNetRequest engine — bypassing the// packaged-rules review path entirely.const existing = await ch.declarativeNetRequest.getDynamicRules();const existingBulkIds = existing.filter(r => r.id >= 11000).map(r => r.id);if (existingBulkIds.length > 0) {  await ch.declarativeNetRequest.updateDynamicRules({ removeRuleIds: existingBulkIds });}await ch.declarativeNetRequest.updateDynamicRules({ addRules: bulkRules });

Remote Server Controls Blocking Rules and Site Allowlist

HighunwantedCWE-829Dynamic sandbox

On a server-set schedule, the extension checks in and applies whatever returns: ad-blocking rules, an allow/block list, a persistent install ID, no update required.

What actually happens

You did this

The extension's check-in timer (wondercycle) expires and it contacts its update server.

The extension did this

The server returns JSON written directly to storage and applied to the blocking engine: ruleset, allow/block list, and a persistent install ID, all without an update.

The same check-in runs again on the next cycle, so the server can change blocking behavior at any later time.

Captured request

POSThttps://wonderupdates.com/wonder58.php

HTTP 200. The response body contained a 10,295-entry rules array, a whitelistedDomains list, and a wonderinformation persistent identifier, confirmed by a console log reporting the DNR bulk rules were applied directly to the blocking engine with a count of 10,295, and by a chrome.storage.local dump showing all three keys present verbatim afterward.

Headers
Content-Type
application/json
Body
{  "extv": "5.8",  "installDoms": [    "google.com",    "facebook.com"  ],  "navDoms": {    "facebook.com": 2,    "google.com": 1  },  "allowedDomains": [],  "blockedDomains": [],  "extid": "fpkbnjejghdcncegfglnapabnljcimdc"}

Keys written verbatim from the server's response into chrome.storage.local

  • Ad-blocking rule count
    10,295 rules (confirmed via console output during dynamic analysis)

    The number of rules currently enforced in your browser is decided entirely by what the server returned on the last check-in.

  • Site allow/block list
    whitelistedDomains key present in storage (illustrative — exact site list not captured)

    Domains the server marks as allowed or blocked, taking effect the next time the extension syncs.

  • Persistent install identifier
    wonderinformation key present in storage (illustrative — exact ID value not captured)

    A stable ID assigned by the server that lets it recognize this specific installation on every future check-in.

The code that does this

fetchData() response handling, src/helper/utils.js

Readable version
// src/helper/utils.js, fetchData() (v5.8)const data = response.data;if (data && typeof data === "object") {  // Store all key/values dynamically from the server response (no authorizedKeys limits)  const payloadToSave = { ...data };  // Note: payloadToSave.rules only contains inline rules (IDs < 11000) from the API.  // Bulk rules (IDs >= 11000) are applied directly to the DNR engine by fetchDnrRulesIfNeeded  // and never stored in chrome.storage.local (which is too slow for 10k+ objects).  payloadToSave.lastUpdateTime = Date.now();  await storage.setItems(payloadToSave);}

Data destination

    • wonderupdates.com

    Update/config server operated by the extension developer. Vends the ad-blocking ruleset, site allow/block list, and a persistent per-installation identifier on every check-in.

Install-Time Tab Snapshot Sent to Developer Server

HighunwantedCWE-359Dynamic sandbox

On install, Ad Block Wonder reads every open tab's domain and sends the list to wonderadblock.com automatically, with no prompt, revealing which sites you were browsing at install.

What actually happens

You did this

You install Ad Block Wonder from the Chrome Web Store.

The extension did this

The extension reads every domain you have open across all your browser tabs and sends the list to the developer's server without a consent prompt.

This happens automatically in the background during first-install setup, before any blocking rules are applied.

Captured request

POSThttps://wonderadblock.com/wonder-3_7.php

HTTP 200, server accepted the payload. Request sent twice during dynamic analysis, both confirmed 200.

Headers
Content-Type
application/json
Body
{  "extv": "3.8",  "installDoms": [    "google.com",    "facebook.com"  ],  "allowedDomains": [],  "extid": "fpkbnjejghdcncegfglnapabnljcimdc"}

What Ad Block Wonder sends on install

  • Your open tab domains
    ["google.com","facebook.com","mail.yahoo.com"]

    The domain of every website you had open at the exact moment you installed the extension. Reveals your browsing session snapshot.

  • Your extension ID
    fpkbnjejghdcncegfglnapabnljcimdc

    The unique identifier for your installation of this extension. Can be used to track you across time.

  • Extension version
    3.8

    Which version of the extension you installed.

  • Your personal allowlist
    []

    Domains you have explicitly whitelisted from ad blocking, also sent on every update request.

The code that does this

The install-time tab collection code (src/helper/utils.js)

Readable version

What the code does in plain terms

// Called immediately when the extension is first installed.async function installDataGathering() {  // Ask Chrome for every open tab in every window — no filter.  const allTabs = await chrome.tabs.query({});  const domains = new Set();  for (const tab of allTabs) {    if (tab.url) {      // Extract just the hostname (e.g. "google.com" from "https://google.com/search?q=...").      const domain = getHostName(tab.url);      if (domain) domains.add(domain);    }  }  // Write the domain list to chrome.storage so fetchData() can include it in the POST body.  if (domains.size > 0) {    await storage.setItem("installDoms", Array.from(domains));  }}// Immediately after, fetchData() reads chrome.storage and POSTs:// { extv, installDoms, allowedDomains, extid } → https://wonderadblock.com/wonder-3_7.php

Where the data ends up

    • wonderadblock.com

    Developer-controlled server receiving every new install's tab-domain snapshot. Also serves subsequent configuration updates and is the uninstall reporting endpoint.

Reproduce it yourself

Intercepts the outbound POST from Ad Block Wonder on install and logs the installDoms payload to the DevTools console, confirming which tab domains were captured.

Requires
  • Chrome with Developer mode enabled
adblock-wonder-install-intercept.js · js
// adblock-wonder-install-spy.js// Intercepts the fetch() call made by Ad Block Wonder on first install// and logs the request body (including installDoms) to the console.//// Run in the DevTools console of the extension's service worker BEFORE installing.(function() {  const originalFetch = self.fetch.bind(self);  self.fetch = async function(input, init) {    const url = typeof input === 'string' ? input : input?.url;    if (url && url.includes('wonderadblock.com')) {      try {        const body = init?.body;        console.log('[WONDER_INSTALL_SPY] Outbound POST intercepted:', url);        if (body) {          const parsed = JSON.parse(body);          console.log('[WONDER_INSTALL_SPY] installDoms:', parsed.installDoms);          console.log('[WONDER_INSTALL_SPY] extid:', parsed.extid);          console.log('[WONDER_INSTALL_SPY] Full body:', JSON.stringify(parsed, null, 2));        }      } catch (e) {        console.error('[WONDER_INSTALL_SPY] Failed to parse body:', e);      }    }    return originalFetch(input, init);  };  console.log('[WONDER_INSTALL_SPY] Installed. Remove and reinstall Ad Block Wonder to capture the install payload.');})();
How to run it
  1. 1Open chrome://extensions, enable Developer mode.
  2. 2Click Ad Block Wonder's service worker link.
  3. 3Paste script in console, press Enter.
  4. 4Remove and reinstall.
  5. 5Watch for WONDER_INSTALL_INTERCEPT logs showing captured installDoms.

+7 more findings not shown

If you have Ad Block Wonder installed

  1. Open chrome://extensions and turn on Developer mode to show IDs. Find the one with ID fpkbnjejghdcncegfglnapabnljcimdc and choose Remove.
  2. Block the servers only it was seen contacting: wonderupdates.com.
  3. Scan your browser to check the rest of your extensions.

Ad Block Wonder version history

  1. 3.7

    Mar 4, 2026

  2. +3 more

  3. 5.5

    May 25, 2026

  4. 5.8

    Jul 3, 2026

  5. 6.0

    Oct 5, 2026

Where Ad Block Wonder sends data

  • wonderupdates.com/…22 calls

    From its background script · only this extension

  • wonderupdates.com/compiled_rules.php19 calls

    From its background script · only this extension

  • wonderupdates.com/cosmetic_css_cache.css15 calls

    From its background script · only this extension

  • wonderupdates.com/wonder58.php14 calls

    From its background script · only this extension

  • fonts.gstatic.com/s/outfit/…6 calls

    From its own pages · 319 other extensions

  • wonderupdates.com/wonder-5_5.php4 calls

    From its background script · only this extension

  • fonts.googleapis.com/css23 calls

    From its own pages · 378 other extensions

  • wonderupdates.com/wonder57.php3 calls

    From its background script · only this extension

Chrome Web Store listing

Versions
6.0 latest of 7 seen since March 4, 2026
Store rating
4.3 from 189 ratings
Last updated
May 21, 2026
Size
7.42 MiB
Privacy policy
wonderadblock.com
Updated November 20, 2026