Is 1Click Browser Guard safe?

Medium risk

1Click Browser Guard is medium risk.

1Click Browser Guard injects scripts into every site and sends per-tab ad-traffic tickets to its servers.

On every page, the extension hooks the page's fetch and XMLHttpRequest calls to observe requests and ad activity, and its service worker posts the resulting per-tab records, including the page URL, to 1clickvpn.com. A separate safe-browsing module is able to send each navigation's URL, title, referrer, request headers and OS to a second 1clickvpn.com host; it ships switched off and is turned on by code. Which sites are watched is set by remote configuration, and the exact contents of the encoded ticket payload were not decoded.

developerv1.1.0Extension ID hpfehpfncjfkfalofhfmeobbicagflchChrome Web Store
49Risk
Who publishes it

developer - 3 other listings from the same operator, 2 of them carrying a finding

Publisher
developer

Same store account

3 other listings published from this account, 402k+ users between them. 2 of them carry a finding.

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.

getsugar.io
Also called by 2 other listings, including Sugar - Smart Shopping Assistant
AI-assisted analysis.

1Click Browser Guard findings

Browser Guard hooks page requests on every site and posts tickets to its vendor

HighunwantedCWE-359Static analysis

Code analysis shows page scripts that watch fetch and XHR traffic on every site, and a service worker that posts per-tab tickets with page URLs to ads-analytics-toolbar.1clickvpn.com.

What actually happens

You did this

You browse any website with the extension installed.

No click or setting is needed.

The extension did this

Requests seen on the page are summarised into a ticket that includes the page URL and is posted to the vendor.

Only url and ad or video counts were seen assembled; the rest of the body is encoded.

Data seen being assembled into tickets

  • Page address
    https://www.example.com/watch?v=abc123

    The address of the page in the tab the ticket describes.

  • Request URLs and method
    GET https://cdn.example.com/video/seg1.mp4

    Addresses and methods of fetch and XHR calls the page makes.

  • Ad and video counts
    ads: 3, video: 12

    How many ads and video requests were detected on the page.

  • Partner and analytics IDs
    pnldsk:1-20-20-<analyticsId>

    Identifiers carried in the Basic auth header with each upload.

The code that does this

Page-world hook on XMLHttpRequest reporting completed requests

Readable version

Readable form

executors/200.js
// executors/200.js, injected into the page's own JavaScript contextconst origOpen = XMLHttpRequest.prototype.open;XMLHttpRequest.prototype.open = function () {  this.requestMethod = arguments[0];      // remember GET/POST  origOpen.apply(this, arguments);};const origSend = XMLHttpRequest.prototype.send;XMLHttpRequest.prototype.send = function () {  const prev = this.onreadystatechange;  this.onreadystatechange = function () {    // when a request completes (readyState 4) and its URL is not on the    // config blacklist, report method, URL, content-type and response body (Y)    if (this.readyState === 4 && !isBlacklisted(this.responseURL))      Y(this.requestMethod, this.responseURL,        this.getResponseHeader('content-type'), this.response, arguments);    if (prev) return prev.apply(this, arguments);  };  return origSend.apply(this, arguments);};

The code that does this

Service worker upload of tickets to the vendor endpoint

Readable version

Readable form

service-worker/index.js
// service-worker/index.js// i.wl = "https://ads-analytics-toolbar.1clickvpn.com"// i.dl = "/tickets"async sendMultiOutTicketToBackend(authHeader, ticket, onOk, onErr) {  const disabled = await this.settings.isDisabled();  if (disabled) onOk();  else if (ticket && ticket.data && authHeader && authHeader.length) {    const endpoint = i.wl + i.dl;   // https://ads-analytics-toolbar.1clickvpn.com/tickets    try {      const res = await this.sendDataToEndpoint(authHeader, ticket.data, endpoint);      this.handleResponse(res, onOk, onErr);    } catch (e) { onErr(e.message); }  }  return disabled;}

Third-party destinations

    • ads-analytics-toolbar.1clickvpn.com

    Serves /configuration and receives /tickets uploads. Same brand domain as the extension homepage.

    • id.1clickvpn.com

    Identity service referenced in the same config class.

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.

Where 1Click Browser Guard sends data

  • ads-analytics-toolbar.1clickvpn.com

    Found in its code · only this extension

  • malware-toolbar.1clickvpn.com

    Found in its code · only this extension

Chrome Web Store listing

Versions
1.0.0 seen since October 28, 2026
Last updated
October 31, 2026
Size
1.07 MiB
Privacy policy
www.1clickvpn.com
Updated November 19, 2026