Is Web ad blocker safe?

Medium risk

Web AdBlocker is medium risk. Code analysis shows the extension takes jobs from metaextension.ads-collect.com, collects LinkedIn Ad Library ad details and posts them back. Not confirmed in a live run.…

webadblockerpluginv3.3.3Extension ID linepocmmjmnmfepinfkfdbmcndjfafbChrome Web Store
54Risk
Who publishes it

webadblockerplugin - 2 other listings from the same operator, 1 of them carrying a finding

Publisher
webadblockerplugin

Same store account

2 other listings published from this account, 50 users between them. 1 of them carries a finding.

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.

metaextension.ads-collect.com
Also called by 3 other listings, including Ad Blocker, Social media Ad finder
AI-assisted analysis.

Web AdBlocker findings

Extension uploads scraped LinkedIn Ad Library results to a remote server

MediumunwantedCWE-359Static analysis

Code analysis shows the extension takes jobs from metaextension.ads-collect.com, collects LinkedIn Ad Library ad details and posts them back.

What actually happens

You did this

The extension asks metaextension.ads-collect.com for a LinkedIn query.

The extension did this

If told to scrape, it collects LinkedIn Ad Library ads and posts them back.

The code that does this

Job polling and ad upload in background.js

Readable version
collectLinkedinAds() runs only when shouldScrap is true; updateLinkedinProcessStatus() posts the ads array to update-linkedin-status.

Fields in the upload request

  • Ads array
    ads: [{domain, title, mediaContent}]

    Ad details collected from the LinkedIn Ad Library.

  • Request ID
    requestId: 51007

    Ties the upload to the server-issued job.

  • Success flag
    success: true

    Whether collection succeeded.

Where the data is sent

    • metaextension.ads-collect.com

    Issues scraping jobs and receives the collected ad data with a bearer token.

Observation

Static analysis finding. This behaviour was identified by reading the shipped extension code and has not yet been reproduced in a live run. The trigger conditions and the exact data sent are read from the code, not from an observed capture.

Web ad blocker fetches remote scraping orders on every Google search

MediumunwantedCWE-829Dynamic sandbox

This ad blocker fetches scraping orders from a remote server every time you load a Google search page.

What actually happens

You did this

You open any Google search results page.

This works on google.com and 180+ country-specific Google search domains.

The extension did this

A content script fires immediately and asks the background service worker to fetch scraping orders from a remote server.

No button click, popup, or other interaction with the extension is required.

Captured request

GEThttps://metaextension.ads-collect.com/adscollector/get-meta-query

200 OK, body {"shouldScrap":false,"data":null}. The request fired within the same second the search page finished loading, before any interaction with the page.

Headers
Accept
application/json
Content-Type
application/json
Authorization
Bearer <redacted>

The code that does this

The remote server's answer is dropped straight into the scraper's config

Readable version
const prodBaseUrl = 'https://metaextension.ads-collect.com'const BASE_URL = `${prodBaseUrl}/adscollector`const API_ENDPOINTS = {    GET_QUERY: `${BASE_URL}/get-meta-query`,    AUTHORIZATION_TOKEN: '<redacted, hardcoded, identical for every install>'}const getQuery = async () => {    try {        return await sendRequest('getQuery', {            url: API_ENDPOINTS.GET_QUERY,            method: 'GET',            headers: {                "Authorization": `Bearer ${API_ENDPOINTS.AUTHORIZATION_TOKEN}`            },            responseType: 'json'        })    } catch (err) {        throw err    }}async function collectAds() {    try {        if (isScraping) return;        isScraping = true;        const query = await getQuery();        if (!query.shouldScrap) {            isScraping = false;            return;        }        await MetaAdsLibrary.initialise(query.data);    } catch (err) {        console.log("Error While Collecting Ads:", err);        isScraping = false;    }}

What the remote server controls on every run

  • Search keyword
    "burger delivery offer"

    Sets the exact term the extension looks up in Facebook's ad library from your browser.

  • Country / country code
    "US" / "GB"

    Picks which country's ad library your browser is told to scrape.

  • Ad type & platform
    "POLITICAL_AND_ISSUE_ADS", "FACEBOOK"

    Narrows the scrape to a specific ad category and platform.

  • Date range
    2026-08-01 to 2026-09-01

    Sets the start and end dates for the ads your browser is told to pull.

  • Result count
    50

    Caps how many ads the extension retrieves in this pass.

  • Request / query ID
    req_8841f2 / dq_20260908_03

    Tags the run so the server can match results back to its own job queue.

Where the traffic goes

    • metaextension.ads-collect.com

    Issues the scraping orders on every Google search and receives the scraped ad data back.

    • facebook.com

    Ad Library GraphQL endpoint queried for ad creative and targeting data on the server's orders.

    • linkedin.com

    Ad Library endpoint queried the same way, under a parallel remote-controlled flow.

Reproduce it yourself

Replays the same unprompted GET the extension fires on every Google search, and prints whatever scraping orders the remote server currently returns.

Requires
  • Node.js 18+
check-scrape-orders.js · js
// check-scrape-orders.js// Replays the request this "ad blocker" extension fires automatically// on every Google search page load, and prints the server's answer.// Node.js 18+ (built-in fetch). Omits the extension's own hardcoded// bearer token; the endpoint answered without it during our test.const ENDPOINT = "https://metaextension.ads-collect.com/adscollector/get-meta-query";async function main() {  const res = await fetch(ENDPOINT, {    method: "GET",    headers: {      "Accept": "application/json",      "Content-Type": "application/json",    },  });  const body = await res.json().catch(() => null);  console.log(`HTTP ${res.status}`);  console.log(JSON.stringify(body, null, 2));  if (body && body.shouldScrap) {    console.log("\nServer is CURRENTLY ARMED with live scraping parameters:");    console.log(JSON.stringify(body.data, null, 2));  } else {    console.log("\nServer declined to arm scraping in this check (shouldScrap is false or missing).");  }}main().catch((err) => {  console.error("Request failed:", err.message);  process.exit(1);});
How to run it
  1. 1Install Node.js 18 or newer.
  2. 2Run node check-scrape-orders.js.
  3. 3Read the printed shouldScrap value: true means live scraping orders were returned.

Extension polls a remote server for jobs and uploads raw Meta Ad Library data

MediumunwantedCWE-359Static analysis

Code analysis shows the extension fetches queries from metaextension.ads-collect.com, collects Meta Ad Library data and posts the raw results back.

What actually happens

You did this

The extension asks metaextension.ads-collect.com for a query to run.

The extension did this

If told to scrape, it collects Meta Ad Library data and posts the raw results back.

The code that does this

Job polling and raw data upload in background.js

Readable version
getQuery() issues a GET with a hardcoded bearer token; addRawData() posts requestId, rawData, source and country to the add-raw-data endpoint.

Fields in the upload request

  • Raw ad data
    rawData: {...Ad Library JSON...}

    Raw Ad Library API responses are sent as received.

  • Request ID
    requestId: 48213

    Ties the upload to the server-issued job.

  • Country
    country: US

    Country of the ad search.

Where the data is sent

    • metaextension.ads-collect.com

    Issues scraping jobs and receives the collected ad data with a bearer token.

Observation

Static analysis finding. This behaviour was identified by reading the shipped extension code and has not yet been reproduced in a live run. The trigger conditions and the exact data sent are read from the code, not from an observed capture.

What Web AdBlocker can do

Permissions this extension asks for, as declared in version 3.3.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

    *://*/*

  • See the address and title of every tab you have open

    tabs

  • Store data in your browser

    storage

  • Block and redirect the requests your browser makes

    declarativeNetRequest

  • Show you desktop notifications

    notifications

Where Web AdBlocker sends data

  • metaextension.ads-collect.com/adscollector/get-linkedin-query4 calls

    From its background script · 1 other extension

  • metaextension.ads-collect.com/adscollector/get-meta-query4 calls

    From its background script · 1 other extension

  • fonts.googleapis.com/css22 calls

    From its own pages · 378 other extensions

  • fonts.gstatic.com/s/poppins/…2 calls

    From its own pages · 319 other extensions

  • metaextension.ads-collect.com/adscollector/update-status2 calls

    From its background script · 1 other extension

  • www.facebook.com/ads/library2 calls

    From its background script · 28 other extensions

Chrome Web Store listing

Versions
3.3.3 seen since March 4, 2026
Store rating
3.4 from 36 ratings
Last updated
November 17, 2025
Size
1.93 MiB
Privacy policy
drive.google.com
Updated November 20, 2026