Is aBlock - Ads Blocker safe?

High risk

aBlock - Ads Blocker is high risk. aBlock sends ablock-ads.com a device ID that never changes on install, update, startup, and every 5 minutes after. A flagged response can make the next startup open an ablock-ads.com popup, unprompted.…

pearlgraha15v2026.6.11Chrome Web Store
69Risk

AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.

Publishers can request a review.

Findings

aBlock beacons a persistent device ID to ablock-ads.com on every startup

aBlock sends ablock-ads.com a device ID that never changes on install, update, startup, and every 5 minutes after.

A flagged response can make the next startup open an ablock-ads.com popup, unprompted.

Severity
Medium unwanted
Type
Unexpected
CWE
CWE-359
Source
Dynamic sandbox
What actually happens
You did this

You install aBlock, update it, start Chrome with it enabled, or leave Chrome running.

The extension did this

aBlock sends ablock-ads.com a request carrying a device ID that stays the same across every request.

The extension's own source code comments describe it as a clean ad blocker with no data collection or analytics.

Captured request
POSThttps://ablock-ads.com/manifest

404 in our test session; a live server is expected to return configVersion and a features object.

Headers
Content-Type
application/json
Body
{  "lastConfigVersion": 0,  "version": "2026.6.11",  "event": "install",  "pusherId": "baa6fa1d"}
Fields sent to ablock-ads.com on every check-in
  • Persistent device ID
    baa6fa1d

    A random ID generated once and reused for every request, letting ablock-ads.com recognize your browser across sessions.

  • Extension version
    2026.6.11

    Tells the server exactly which aBlock version you're running.

  • Lifecycle event
    install

    Tells the server whether this is a fresh install, an update, a startup, or a periodic check-in.

  • Last config version seen
    0

    Lets the server know what configuration you last received.

When this fires

Every 5 minutes

After the install/startup beacon, aBlock checks in with ablock-ads.com every 5 minutes for as long as Chrome runs.

A remote flag can open a popup on a later startup

A specific server response value makes aBlock open an ablock-ads.com popup carrying your device ID on the next startup, unprompted. Our test server returned a 404, so only the beaconing and the code path that reads the flag were confirmed.

Where this data goes
    • ablock-ads.com

    Receives a persistent per-install ID on every install, update, startup, and 5-minute check-in, and is the destination for the uninstall survey and any server-triggered popup.

Updated 21 September 2026dihpglgcjgbocmfckenaideddpkhhlmi