Is AdBlocker Professional safe?
AdBlocker Professional is medium risk. Code analysis shows the extension fetches settings from adblockerprofessional.com and replays stored codeBlock entries as page events. No signature check was found; the response body was not captured.…
AdBlocker Professional findings
AdBlocker Professional acts on remote settings with no integrity checks
Code analysis shows the extension fetches settings from adblockerprofessional.com and replays stored codeBlock entries as page events.
No signature check was found; the response body was not captured.
What actually happens
You open a page on a site that has an entry in stored settings.
The extension dispatches each stored codeBlock entry into the page as a CustomEvent.
Event names and parameters come from the downloaded settings.
The code that does this
Stored entries become page events
Readable equivalent
isolated.jsfor (const entry of stored.codeBlock) { const eventName = Object.keys(entry)[0]; const params = entry[eventName]; document.dispatchEvent(new CustomEvent(eventName, { detail: { params } }));}Remote settings source
- adblockerprofessional.com
Serves the settings URL under /maj/net_data/ that is fetched and stored locally.
Observation
Four requests to the settings endpoint returned status 200 during dynamic analysis, but response bodies were not captured. What the server returns is unverified.
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.
Unique tracking ID assigned on install, sent to developer server
On install, Adblocker Professional contacts the developer's server and gets a permanent unique identifier tied to your install.
It's stored locally and sent in every check-in, letting the developer track you over time.
Undisclosed anywhere.
What actually happens
You install the extension for the first time.
The extension immediately contacts the developer's server, receives a permanent unique identifier, and stores it on your device.
The ID is also embedded in the extension's uninstall notification URL so the developer is notified when you remove it.
Captured request
JSON object containing uniqueUserId field, a stable, server-assigned identifier for this installation.
- credentials
- include
What's stored on your device
A base64-encoded unique installation identifier assigned by the developer's server on first install; sent in every later periodic beacon.
- Location
- chrome.storage.local key 'userId'
ai9WZkg2SXJUU20veDY0QTU5UmhKeUhYM0p2UU1NR0I3bmlobFBnNGtCYTBuOEFLTEVtd2wwSXF1ckluLzF3MmFDeDAvTFVjThe code that does this
Install handler assigns and stores the tracking ID
chrome.runtime.onInstalled.addListener(async (event) => { if (event.reason === chrome.runtime.OnInstalledReason.INSTALL) { let userId = 'default'; try { const response = await fetch( 'https://adblockerprofessional.com/install/?version=' + encodeURIComponent(chrome.runtime.getManifest().version), { credentials: 'include' } ); const data = await response.json(); userId = data.uniqueUserId; // server-assigned tracking ID } finally { await chrome.storage.local.set({ userId }); // persisted locally chrome.runtime.setUninstallURL( 'https://adblockerprofessional.com/un/?uniqueUserId=' + userId // notifies on uninstall ); } }});Where the install event is reported
- adblockerprofessional.com
Developer's own server. Receives the install event and issues the uniqueUserId. Also receives the uninstall notification and all subsequent periodic beacons.
Persistent tracking ID transmitted to developer server every hour
Adblocker Professional sends your permanent installation ID to the developer's server about once an hour.
The ID never changes, letting the developer build a long-term activity record tied to your device, with no notification.
What actually happens
The extension's internal alarm fires every 60 minutes.
The extension reads your stored unique identifier and sends it to the developer's server along with the extension version.
The same identifier is reused each time, making every beacon linkable to the same installation.
Captured request
JSON object with network filter configuration data (id, url, v fields). The same uniqueUserId token appeared in 4 consecutive requests during dynamic analysis.
- credentials
- include
When this fires
Every 1 day
Beacon fires at most once every 24 hours per the updateNetDataLastRunDate cooldown. With the alarm set to every 60 minutes, the beacon goes out on the first alarm tick after the 24-hour window expires.
The code that does this
Periodic beacon function transmits the stored tracking ID
const sendNetDataBeacon = async () => { let { userId, updateNetDataLastRunDate: lastRun } = await chrome.storage.local.get(['userId', 'updateNetDataLastRunDate']); if (!lastRun) lastRun = 0; // 24-hour cooldown if (lastRun && Date.now() - lastRun < 24 * 3600 * 1000) return; try { const result = await fetch( 'https://adblockerprofessional.com/maj/net_data/?' + 'uniqueUserId=' + userId + '&version=' + encodeURIComponent(chrome.runtime.getManifest().version), { credentials: 'include' } ); // ... processes network filter config from response ... } finally { await chrome.storage.local.set({ updateNetDataLastRunDate: Date.now() }); }};Data transmitted in each periodic beacon
- Unique installation IDai9WZkg2SXJUU20veDY0QTU5UmhKeUhYM0p2UU1NR0I3bmlobFBnNGtCYTBuOEFLTEVtd2wwSXF1ckluLzF3MmFDeDAvTFVj
Stable ID assigned by the developer's server on first install, reused in every request to link all beacons to the same device.
- Extension version2.0.2.3
The currently installed version number. Lets the developer know which release is active on each tracked installation.
Destination for periodic tracking beacons
- adblockerprofessional.com
Developer's own server. Receives uniqueUserId and version each periodic check-in (at most once per 24h), plus the install ping and uninstall notice.
What AdBlocker Professional can do
Permissions this extension asks for, as declared in version 2.0.2.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
<all_urls>
Block and redirect the requests your browser makes
declarativeNetRequest
Run its own code inside the pages you visit
scripting
Store data in your browser
storage
Store an unlimited amount of data in your browser
unlimitedStorage
Schedule its own background tasks
alarms
Where AdBlocker Professional sends data
- adblockerprofessional.com/maj/net4 calls
From its background script · only this extension
- adblockerprofessional.com/maj/net_data4 calls
From its background script · only this extension
- adblockerprofessional.com/install3 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.2.3 seen since March 4, 2026
- Store rating
- 3.8 from 21 ratings
- Last updated
- September 30, 2025
- Size
- 2.77 MiB
- Privacy policy
- adblockerprofessional.com
