Is BlockSite Block Websites & Stay Focused safe?
Block Site is high risk. The moment BlockSite finishes installing, it reads every open tab's URL and sends them to statistics.blocksite.co, no prompt. The request fires from the install handler, no interaction. Only HTTP/HTTPS URLs, but any open page is captured.…
Who publishes itBlockSite LP - no other listings under this identity, 1 shared hostname
BlockSite LP - no other listings under this identity, 1 shared hostname
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.
Block Site findings
BlockSite Collects All Open Tab URLs on Install
The moment BlockSite finishes installing, it reads every open tab's URL and sends them to statistics.blocksite.co, no prompt.
The request fires from the install handler, no interaction.
Only HTTP/HTTPS URLs, but any open page is captured.
What actually happens
You install BlockSite from the Chrome Web Store.
The extension immediately reads all open tab URLs in your current window and POSTs them to statistics.blocksite.co.
No user interaction is needed beyond installation. The collection happens before you have opened BlockSite's settings or accepted any prompt.
Captured request
Observed during dynamic analysis, fired ~2 seconds after install. No Authorization header present.
- Content-Type
- application/json
{ "urls": [ "https://www.google.com/account/about/?hl=en-US", "https://www.facebook.com/" ], "platform": "extension", "timestamp": 1780652280218, "eventType": "install"}What BlockSite sends at install time
- All open tab URLshttps://www.google.com/account/about/?hl=en-US
Every HTTP or HTTPS page you have open in your current window at the moment of installation.
- Platform identifierextension
Hardcoded string identifying this as the browser extension client.
- Install timestamp1780652280218
Millisecond-precision timestamp of when installation occurred.
- Event typeinstall
Hardcoded label classifying this as an install-time event.
The code that does this
The install handler that collects and transmits tab URLs
// Fires from chrome.runtime.onInstalled handlerasync function sendInstallEvent() { // One-shot guard: skip if already sent const alreadyFired = await storage.get(STORAGE_KEYS.IS_INSTALL_EVENT_FIRED); if (alreadyFired) return; try { chrome.tabs.query({ currentWindow: true }, (tabs) => { // Collect all HTTP/HTTPS tab URLs const urls = tabs .map(tab => tab.url) .filter(url => url.indexOf('http') === 0); if (urls.length) { fetch(STATISTICS_SERVICE + '/event/createOnInstallEvent', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ urls, platform: 'extension', timestamp: Date.now(), eventType: 'install' }) // No Authorization header }); } }); } catch (e) { logger.error('failed to send install event', e); } // Mark as sent so it never fires again await storage.set(STORAGE_KEYS.IS_INSTALL_EVENT_FIRED, true);}Where the tab URLs are sent
- statistics.blocksite.co
BlockSite's own analytics backend. Receives the install-time tab URL payload with no authentication. Owned and operated by BlockSite (Artium Technologies Ltd.).
BlockSite's Braze SDK can log each site's domain to Braze, behind a server flag
Code analysis shows a Braze page_view event carrying the site's domain can be sent on navigation, tied to your Firebase user ID.
It was off server-side when tested, so no transmission was observed.
What actually happens
You visit a website while the extension is installed.
If the server flag is on, the extension logs a page_view event with that site's domain to Braze, linked to your account ID.
The code that does this
Content script init path and Braze event call
Init path
content.jsconst host = URI.parse(window.location.host);await brazeClient.firePageViewEvent(host.domain);await brazeClient.sendEvent(EXTENSION_SESSION);Event call
content.jsasync firePageViewEvent(website) { if (!this.isReady('firePageViewEvent')) return; this.brazeInstance.logCustomEvent('page_view', { website });}Data in the page_view event
- Website domainexample.com
The domain of the site you are on.
- Firebase user IDchangeUser(uid)
Links the event to your account.
Destination
- sdk.iad-07.braze.com
Braze customer engagement platform; receives the page_view event and session data.
- feature-flag.blocksite.co
Extension vendor server that decides whether the SDK starts in the content script.
What was and was not observed
The server flag was off in two dynamic analysis sessions, including across navigations to several sites. No requests to the Braze endpoint came from the content script. The behaviour depends on the vendor enabling the flag.
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.
BlockSite reads the full contents of every web response on every page
BlockSite adds a script to every web page before the page's own code runs and copies every response, even with no blocking rule.
Captured addresses and bodies are checked against a rule list from a remote server.
What actually happens
You open any website while BlockSite is installed.
BlockSite injects a script into the page's own JS context that overrides fetch and XHR.send to read the full body of every response the page receives.
This runs on every http(s) page, whether or not BlockSite has a blocking rule configured for that specific site.
The code that does this
The XHR interceptor that reads and broadcasts every response body
// Installed by overwriting XMLHttpRequest.prototype.send, once per request instance.// Runs inside the PAGE's own JavaScript context (injected via a <script> tag),// not the extension's isolated content-script world.function patchedSend() { this.addEventListener('load', function () { let responseBody = null; try { responseBody = this.responseText; // the full response body, read unconditionally } catch (e) {} // Broadcast the captured body + request URL as a page-level DOM event const captureEvent = new CustomEvent('active-content-block', { detail: { way: 'xhr', event: responseBody, url: this.__requestUrl } }); self.dispatchEvent(captureEvent); }); originalSend.apply(this, arguments); // A 1-second no-op timeout follows in the shipped build; it has no // observable effect on the capture itself.}Captured request
Observed during dynamic analysis: 200 OK, roughly 235 KB of JSON. The response is stored under chrome.storage.local key 'cDXLl' and, unless it already carries a 'type' field, is decoded via a custom transposition-plus-base64 scheme before use, the on-disk copy is deliberately obscured against casual inspection.
{ "sid": "a6cf643b7"}What the interceptor reads on every page
- Full response body text(illustrative) {"account":{"email":"jane@example.com","plan":"pro"}}
The complete text of every response an XHR or fetch call on the page receives, API responses, account data, or anything else the site loads.
- Request and page URLhttps://mail.example.com/api/v3/inbox?page=1
The exact address of the page you're on and the specific API endpoint being called.
- Obfuscated rule listchrome.storage.local key 'cDXLl' (encoded)
A remotely-updatable list of URL and content patterns BlockSite uses to decide what to do with a captured response.
- Rule refresh interval21600000 ms (6 hours)
How often BlockSite checks BlockSite's own server for an updated rule list.
What we did and didn't confirm
We confirmed the XHR response-body capture is unconditional — it fires on a page with no matching BlockSite rule — by dispatching a plain request on such a page and observing the capture event with the full response body. The fetch-response capture path only activates once a rule's URL pattern matches the page. The rule source is BlockSite's own backend, and the rule engine we read also handles video-ad-detection ('VAST') rule types, so this mechanism can plausibly power a legitimate content-filtering feature rather than exist solely to collect page data. What we flag is the scope and design: full-body network interception across every website, remotely retargetable by BlockSite at any time, with the on-disk configuration deliberately obscured from casual inspection. We did not trace whether a matched capture is ever transmitted off the device beyond the internal chrome.runtime.sendMessage call to BlockSite's own service worker.
Reproduce it yourself
Listens for BlockSite's internal capture event and issues a normal same-origin fetch to show the interceptor runs even on a page with no matching BlockSite rule.
- Chrome with BlockSite extension installed
- Any http(s) page loaded
// blocksite-response-capture-check.js// Run in the DevTools console of ANY http(s) page while BlockSite is installed,// including a page with no BlockSite blocking rule for it.self.addEventListener('active-content-block', (e) => { console.log('[BLOCKSITE-INTERCEPT] captured response:', e.detail);});// Trigger any request the page would normally make. A same-origin fetch works.fetch(location.origin + '/', { method: 'GET' }).catch(() => {});- 1Install BlockSite, open any http(s) page (no rule needed).
- 2Open DevTools, Console.
- 3Paste and run this script.
- 4Reload or trigger a request.
- 5The response body/URL log, confirming BlockSite read it.
+1 more finding not shown
If you have Block Site installed
- Open
chrome://extensionsand turn on Developer mode to show IDs. Find the one with IDeiimnmioipafcokbfikbljfdeojpcgbhand choose Remove. - Block the servers only it was seen contacting:
blocksite-cdn.s3.amazonaws.com. - Scan your browser to check the rest of your extensions.
What Block Site can do
Permissions this extension asks for, as declared in version 7.1.1. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to. The current listed version is 8.1.0, which we have not unpacked yet.
Read and change your data on every site you visit
<all_urls>
See the address and title of every tab you have open
tabs
Block and redirect the requests your browser makes
declarativeNetRequest
Store data in your browser
storage
Store an unlimited amount of data in your browser
unlimitedStorage
Add items to the right-click menu
contextMenus
Show you desktop notifications
notifications
Watch every request your browser makes
webRequest
See every page you navigate to, as you navigate to it
webNavigation
Read and change cookies, including the ones that keep you signed in
cookies
Run its own code inside the pages you visit
scripting
Schedule its own background tasks
alarms
Detect when you step away from your computer
idle
Block Site version history
6.9.9
Mar 4, 2026
+4 more
8.0.0
Nov 4, 2026
8.0.1
Nov 6, 2026
8.1.0
Nov 20, 2026
Where Block Site sends data
- api-js.mixpanel.com/track10 calls
From its own pages · 17 other extensions
- user-state.blocksite.co/user-config9 calls
From its background script · 1 other extension
- user-state.blocksite.co/state/save8 calls
From its background script · 1 other extension
- api.mixpanel.com/engage7 calls
From its background script · 22 other extensions
- feature-flag.blocksite.co/features7 calls
From a script it injects into websites · 1 other extension
- v.redd.it/…7 calls
From a script it injects into websites · 4 other extensions
- analytics.blocksite.co/v2/event6 calls
From its background script · 1 other extension
- gtm.blocksite.co/extension_trk6 calls
From its background script · 1 other extension
- identitytoolkit.googleapis.com/v1/accounts:lookup6 calls
From its background script · 9 other extensions
- statistics.blocksite.co/event/createOnInstallEvent6 calls
From its background script · 1 other extension
- identitytoolkit.googleapis.com/v1/accounts:signUp5 calls
From its background script · 9 other extensions
- category.blocksite.co/category4 calls
From its background script · 1 other extension
- category.blocksite.co/sites/blockrate4 calls
From its background script · 1 other extension
- category.blocksite.co/v2/config4 calls
From its background script · 1 other extension
- sdk.iad-07.braze.com/api/v3/…4 calls
From its own pages · 1 other extension
- www.google.com/s2/favicons4 calls
From its own pages · 108 other extensions
- wa.onelink.me/v1/onelink3 calls
From a script it injects into websites · 4 other extensions
- www.amazon.com/cart/add-to-cart/…3 calls
From a script it injects into websites · 55 other extensions
- blocksite-cdn.s3.amazonaws.com/Campaign-images/summer_sale_2.png2 calls
From its own pages · only this extension
- category.blocksite.co/block/settings2 calls
From its background script · 1 other extension
- edge.fullstory.com/s/settings/…2 calls
From a script it injects into websites · 1 other extension
- fonts.googleapis.com/css2 calls
From its own pages · 378 other extensions
- fonts.gstatic.com/s/inter/…2 calls
From its own pages · 319 other extensions
- h.clarity.ms/collect2 calls
From a script it injects into websites · 3 other extensions
- px.ads.linkedin.com/attribution_trigger2 calls
From a script it injects into websites · 4 other extensions
Named inside its requests but not contacted (servers it tested or reported on): 483008214107-io49o51ekp7qff7tcpj1o3idpkdcioq6.apps.googleusercontent.com, user.blocksite.co, website-user.blocksite.co.
Chrome Web Store listing
- Versions
- 8.1.0 latest of 8 seen since March 4, 2026
- Store rating
- 4.5 from 32,066 ratings
- Last updated
- March 29, 2026
- Size
- 19.32 MiB
- Privacy policy
- blocksite.co
