Is Ad Blocker safe?
Ad Blocker is medium risk. Code analysis shows the extension reads the ads and search query on Google results pages and posts them to newbackend.ads-collect.com. A network capture was not obtained.…
Ad Blocker findings
Ad blocker sends Google results-page ads and your query to ads-collect.com
Code analysis shows the extension reads the ads and search query on Google results pages and posts them to newbackend.ads-collect.com.
A network capture was not obtained.
What actually happens
You open a Google search results page that shows ads.
The extension reads the ads and your search text and sends them to ads-collect.com.
Fields collected per ad
- Search querycheap flights to lisbon
The words you searched for, taken from the page title.
- Ad linkhttps://www.example-travel.com/lisbon
Where the ad sends you when clicked.
- Ad title and textFlights to Lisbon from 29 EUR
The ad headline and description shown to you.
- Ad iconhttps://www.example-travel.com/favicon.ico
The small site icon shown beside the ad.
Third-party destinations
- newbackend.ads-collect.com
Receives the JSON array of ads at /api/googleSearch/ad-blocker.
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.
Extension queries Facebook Ads Library with page tokens and uploads raw ad data
Code analysis shows the extension reads Facebook page tokens from an open tab, queries the Ads Library, and posts the raw responses to ads-collect.com.
Not confirmed by observed traffic.
What actually happens
The extension receives a scrape task for the Facebook Ads Library.
It reuses your Facebook page tokens to query the library, then uploads the raw results.
The code that does this
Token extraction and upload call sites
fb_dtsg = fb_dtsg || getMatch(html, /name="fb_dtsg" value="([^"]+)"/)...const rawResponse = await addRawData(this.requestId, adData, this.source, this.country, this.contentLanguages)Data sent to the operator backend
- Ad copyFree shipping this week
The text of each ad found in the library.
- Call-to-action linkhttps://example.com/offer
Where each ad sends people.
- Page and advertiser IDspage_id: 1234567890
Which advertiser published the ad.
- Images and videoshttps://scontent.xx.fbcdn.net/example.jpg
Links to ad media.
Hosts contacted by this code path
- metaextension.ads-collect.com
Operator backend that issues scrape tasks and receives the collected ad data.
- www.facebook.com
Ads Library GraphQL endpoint queried with tokens read from the page.
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.
Extension runs ad scraping tasks dictated by a remote server
Code analysis shows the background script fetches scrape instructions from the vendor's server and carries them out against Facebook and Google ad pages.
Not confirmed by observed traffic.
What actually happens
A page script sends a start_scraping message to the extension.
The extension asks the vendor's server what to collect, then collects it.
The code that does this
Remote task endpoints and bearer header
const prodBaseUrl = 'https://metaextension.ads-collect.com'const BASE_URL = `${prodBaseUrl}/adscollector`const API_ENDPOINTS = { GET_GENERAL_QUERY: `${BASE_URL}/meta/general`, GET_DATE_BASED_QUERY: `${BASE_URL}/meta/date-based`, UPDATE_STATUS: `${BASE_URL}/meta/general/status`, ADD_RAW_DATA: `${BASE_URL}/add-raw-data`, AUTHORIZATION_TOKEN: '<redacted>'}Parameters the server controls
- Scrape flagshouldScrap: true
The server decides whether a scrape happens at all.
- Search queryquery: "example brand"
The server picks the search term used on the ad libraries.
- Countrycountry: "US"
The server picks which country's ads are queried.
- Advertiser listadvertisers: ["Example Page"]
The server supplies which advertisers to collect.
Hosts contacted by this code path
- metaextension.ads-collect.com
Operator backend that issues scrape tasks and receives the collected ad data.
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.
+1 more finding not shown
What Ad Blocker can do
Permissions this extension asks for, as declared in version 2.0.1. 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>
Block and redirect the requests your browser makes
declarativeNetRequest
Store data in your browser
storage
Act on the current tab, but only after you click the extension
activeTab
See which of your requests its blocking rules matched
declarativeNetRequestFeedback
Ad Blocker version history
2.0.0
Mar 4, 2026
2.0.1
Apr 11, 2026
Where Ad Blocker sends data
- displayads-formats.googleusercontent.com/ads/preview/…6 calls
From its background script · only this extension
- adstransparency.google.com/anji/_/…3 calls
From its background script · only this extension
- metaextension.ads-collect.com/adscollector/google/…2 calls
From its background script · 1 other extension
- metaextension.ads-collect.com/adscollector/meta/…2 calls
From its background script · 1 other extension
- adstransparency.google.com1 call
From its background script · only this extension
Named inside its requests but not contacted (servers it tested or reported on): farabiclinics.com.
Chrome Web Store listing
- Versions
- 2.0.1 latest of 2 seen since March 4, 2026
- Store rating
- 4.3 from 62 ratings
- Last updated
- April 9, 2026
- Size
- 1.94 MiB
