Is Hola VPN - Your Website Unblocker safe?
Hola VPN is medium risk.
Hola VPN captures Chrome-internal identity headers from your Google requests and sends them to its servers every 10 minutes.
When the A/B test activates (affecting approximately 51% of Chrome desktop users), the extension registers a listener on all Google requests and reads privileged headers including X-Client-Data — a unique per-install Chrome fingerprint — along with browser channel, validation token, and user-agent. These are batched and uploaded via POST to client.hola.org every 10 minutes. No user action beyond installing the extension is required for collection to begin.
Who publishes itHola VPN LTD. - 2 other listings from the same operator, none carrying a finding
Hola VPN LTD. - 2 other listings from the same operator, none carrying a finding
Same operator - 2 listings
Published under a different store account, but sharing the registered address, contact or declared legal entity this one gave the store.
Shared hosts - 5 hostnames
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.
Hola VPN findings
Hola VPN Harvests Chrome Identity Headers from Google Traffic
Every ten minutes, Hola VPN collects private Chrome headers Google attaches to your requests, including X-Client-Data (a unique install fingerprint), uploaded to Hola's servers.
Gated by an A/B test; starts after install with no prompt.
What actually happens
You install Hola VPN and visit any Google page.
No action beyond install is needed, collection starts automatically once the A/B test activates.
Hola captures private Chrome identity headers from your Google requests and uploads them to its servers every 10 minutes.
X-Client-Data is a unique per-install Chrome fingerprint; Hola collects it without a consent prompt, alongside your browser channel and validation token.
Headers captured from your Google requests
- Chrome Install IDCJOHywE=
A unique identifier tied to your Chrome install. Google uses it for experiments; Hola collecting it fingerprints your browser.
- Browser Channelstable
Identifies whether you are on Chrome Stable, Beta, Dev, or Canary.
- Browser Validation TokenT/cMGWcFBicTCYvDwxRmMQ==
A cryptographic token Chrome sends to Google to prove the request came from a legitimate Chrome build.
- User-AgentMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36
Your full browser version string including OS and Chrome version.
Captured request
29 POST requests observed in dynamic analysis session after A/B flag forced on (rand=0.75); 17 of 29 included X-Client-Data.
- Content-Type
- application/json
{ "X-Client-Data": "CJOHywE=", "X-Browser-Channel": "stable", "X-Browser-Validation": "T/cMGWcFBicTCYvDwxRmMQ==", "User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36"}The code that does this
Chrome_headers class: header collection and upload logic
// Chrome_headers: captures Chrome identity headers from Google requests without a consent promptclass Chrome_headers { constructor(conf) { this.conf = conf; this.data = {}; // accumulates captured headers between flushes this.listener = this._listener.bind(this); } // Called by A/B gate when test_send_chrome_headers value = 'on' activate() { chrome.webRequest.onSendHeaders.addListener( this.listener, { urls: ['*://*.google.com/*'] }, // 'extraHeaders' is required to access privileged Chrome-internal headers // (X-Client-Data is not accessible to extensions without this flag) ['requestHeaders', 'extraHeaders'] ); } deactivate() { try { chrome.webRequest.onSendHeaders.removeListener(this.listener); } catch (e) { /* ignore */ } } // Generator: POSTs accumulated headers to Hola backend every ~10 min *_send() { yield be_bg_ajax.ccgi_ajax({ url: conf.url_ccgi + '/chrome_headers?be_ver=' + version(), method: 'POST', data: this.data // { 'X-Client-Data': 'CJOHywE=', 'User-Agent': '...', ... } }); }}When this fires
Every 10 minutes
Captured headers are flushed to Hola servers on a recurring 10-minute timer. Each flush uploads the accumulated header data from your Google browsing since the last send.
Where your Chrome identity headers are sent
- client.hola.org
Hola Networks' primary API server. Receives harvested Chrome identity headers via POST /client_cgi/chrome_headers. Historically tied to the Bright Data (Luminati) proxy network.
Google x-client-data install ID and headers forwarded to a Hola server
Browsing *.google.com, Hola VPN reads Chrome-internal headers from outgoing requests, x-client-data, four x-browser-* headers, your User-Agent, then POSTs them to client.hola.org/client_cgi/chrome_headers.
New in 1.253.755.
What actually happens
You load any page on a *.google.com domain.
For example google.com, mail.google.com, or drive.google.com in a normal browsing tab.
The extension reads Chrome's internal request headers off that request and sends them to a Hola server.
It captures x-client-data, x-browser-channel, x-browser-copyright, x-browser-validation, x-browser-year and User-Agent, then POSTs them to client.hola.org/client_cgi/chrome_headers.
What is read from each outgoing Google request and forwarded
- Chrome install ID (x-client-data)X-Client-Data: CJOHywE=
A short token Chrome attaches only to Google requests. Forwarding it to a third party lets that party tie your separate visits together.
- Full browser User-AgentMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/146.0.0.0 Safari/537.36
Your exact browser version and platform, with the full Chrome build number spliced in from a Client Hint.
- Chrome build/validation headersX-Browser-Channel: stable; X-Browser-Year: 2025
Four Google-internal headers describing your Chrome channel, copyright year, build year and a validation token.
- Google location-cookie shape (UULE)uule_type: "w+CAIQICI", uule_length: 88
The first 10 characters and total length of your Google UULE cookie, which encodes a location signal, are appended to the payload.
Captured request
Captured during dynamic analysis: 15 POST requests from the background service worker to this endpoint after the A/B flag was set on and google.com was visited. The bodies carried the X-Client-Data token and full Chrome User-Agent string.
- Content-Type
- application/json
{ "User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/146.0.0.0 Safari/537.36", "X-Client-Data": "CJOHywE="}The code that does this
The header-collection class in the background service worker
const chrome_header_names = ["x-browser-channel", "x-browser-copyright", "x-browser-validation", "x-browser-year", "x-client-data", "user-agent"];const google_url_pattern = "*://*.google.com/*";// _add_listener(): capture matching headers off every outgoing Google requestthis.listener = details => { if (!details.requestHeaders) return; const headers = {}; for (const hdr of details.requestHeaders) { if (chrome_header_names.includes(hdr.name.toLowerCase())) { headers[hdr.name] = hdr.value; } } if (!Object.keys(headers).length) return; if (ua_full_ver) { const ua_str = headers["User-Agent"] || headers["user-agent"] || ""; if (ua_str) headers["User-Agent"] = ua_str.replace(/Chrome\/[\d.]+/, "Chrome/" + ua_full_ver); } this.data = headers; this.send();};self.chrome.webRequest.onSendHeaders.addListener( this.listener, { urls: [google_url_pattern] }, ["requestHeaders", "extraHeaders"]);// send(): POST the captured headers to the Hola endpointyield E.be_bg_ajax.ccgi_ajax({ url: conf.url_ccgi + "/chrome_headers?be_ver=" + version(), method: "POST", data: this.data, timeout: 10 * ms.SEC});The code that does this
The server-side A/B flag that gates the feature
// default extension config: collection wiring is present and enabled...collect_chrome_headers: { enabled: true, interval: 6e5 }, // 600,000 ms = 10 min// ...but a server-controlled A/B test decides who actually runs it:test_send_chrome_headers: { ver: 2, min_ver: "1.251.527", value: [[0, 1, "off"], [0, 0, "on"]], filter: { browser: "chrome" }}// gate at update_config():if (ch_ab.test_send_chrome_headers != "on") ch_conf.enabled = false;Where the collected headers are sent
- client.hola.org
Receives the POSTed Chrome request headers at /client_cgi/chrome_headers. Operated by Hola Networks Ltd., the extension's publisher.
Server-controlled gating
This collection is controlled by a server-side A/B flag (test_send_chrome_headers). In our first dynamic-analysis sessions on a fresh profile, the Hola server assigned the flag to off and no headers were collected. After we set the flag to on and visited google.com, the collection fired and we captured the POST requests shown above. Because the flag is decided server-side per install, whether any given user is currently in the collecting group is not visible from the extension UI.
Hola VPN Sends Full Google Rate-Limit Page URLs to Its Telemetry Server
When Google rate-limits/captcha-challenges you ('/sorry/' page, HTTP 429) after a search burst, Hola VPN reads that page's URL, including your search query, and sends it to perr.hola.org.
Confirmed with a marker; fired with no VPN or login.
What actually happens
You run several Google searches quickly enough that Google serves you its rate-limit/captcha page instead of results.
That page is served from a path containing '/sorry/' with an HTTP 429 status, and its redirect URL has your original search query folded into it.
Hola's background service worker reads the full '/sorry/' page URL off the response and sends it to Hola's own telemetry server.
This happens whether or not you are connected to the VPN or logged into a Hola account.
What's sent when Google rate-limits or challenges you
- Captcha/rate-limit page URLhttps://www.google.com/sorry/index?continue=https://www.google.com/search%3Fq%3Dhotel%2Brefund%2Bpolicy (illustrative)
The full address of the page Google sent you to, with your original search query folded into it.
- HTTP status code429
The response code Google returned, always a rate-limit or challenge code for this report to fire.
- Root domaingoogle.com
The site the report is about, parsed from the page URL.
- Response detailsstatusCode: 429, statusLine: "HTTP/1.1 429 Too Many Requests"
The raw response metadata for the page load, including the headers Google sent back.
Captured request
Observed during dynamic analysis: this request fired immediately after navigating to Google's rate-limit page with a planted marker value inserted into the search query. The marker was present verbatim in both the url and page_url fields of the request body, confirming the page URL, and anything encoded in it, leaves the device even though the VPN was never connected and no Hola account was logged in.
- Content-Type
- application/json
{ "is_json": 1, "info": "{\"info\":{\"no_unblock\":true,\"url\":\"https://www.google.com/sorry/index?continue=https://www.google.com/search%3Fq%3D<planted-marker-redacted>\",\"code\":\"429\",\"page_url\":\"https://www.google.com/sorry/index?continue=https://www.google.com/search%3Fq%3D<planted-marker-redacted>\",\"root_url\":\"google.com\",\"details\":{\"statusCode\":429,\"statusLine\":\"HTTP/1.1 429 Too Many Requests\"}}}"}The code that does this
The response-header listener that reports the captcha/rate-limit page URL
on_main_frame_headers (response-header handler)
js/bg.bg.bundle.js// Fired for every main_frame response via chrome.webRequest.onHeadersReceivedconst on_main_frame_headers = d => { let failure; if (!(failure = get_failure_config("browse"))) return; // Only look at 4xx/5xx responses (407 Proxy Auth Required is excluded) if (d.tabId < 0 || !/^(4|5)/.test(d.statusCode) || d.statusCode == 407) return; let tab_url = d.url || d.initiator, root_url; if (tab_url) root_url = svc_vpn_util.get_root_url(tab_url); // 'info' carries the page URL twice (url + page_url) plus the parsed root domain let info = { url: d.url, code: d.statusCode, page_url: tab_url, root_url, details: d }; let is_hola_domain = zurl.is_hola_domain(root_url); let tab = E.get_tab_unblocker(d.tabId), req = E.requests[d.requestId]; let no_unblock = !tab || !req && !is_hola_domain; // Google's captcha/rate-limit page: report the full URL to Hola's telemetry server if (!CG("disable_google_caps_oops") && be_vpn_util.is_google(root_url) && tab_url.includes("/sorry/")) { be_util.perr("google_caps_oops", { info: assign({ no_unblock }, info) }, { rate_limit: { count: 1 } }); } else if (!CG("disable_hola_err") && is_hola_domain) { be_util.perr("hola_browse_failure", { info }, { rate_limit: { count: 1 } }); } if (no_unblock) return; // ...remaining branch tracks unblocker-proxy failure counters, unrelated to this report};perr_send (builds and fires the telemetry POST)
js/bg.bg.bundle.js// Builds and sends every 'perr' (product error/telemetry) eventfunction perr_send(id, info, opt) { opt = zutil.clone(opt || {}); var qs = opt.qs || {}, data = opt.data || {}; data.is_json = 1; // Non-string info (our {url, code, page_url, root_url, details} object) is JSON-stringified if (info && typeof info != "string") info = zerr.json(info); var err = opt.err; if (err) { // ...error-specific formatting, not used for google_caps_oops } data.info = info; qs.id = id; // e.g. 'be_google_caps_oops' opt = { url: conf.url_perr + "/perr", qs, data, method: "POST", json: 1 }; return ajax_cb ? ajax_cb(opt) : ajax(opt);}Where the page URL is sent
- perr.hola.org
Hola Networks' error/telemetry endpoint. Most events carry only internal state (mode, timing, flags); this one sends the full URL of the Google page that triggered the rate-limit.
Scope of this behavior
This report only fires when a page on a google.com domain returns an HTTP 4xx or 5xx response and the URL path contains "/sorry/" — Google's automated-traffic rate-limit and captcha page. We did not find this event firing for ordinary Google page loads that return a normal response, and it is separate from the extension's general telemetry stream, which otherwise carries connection mode, timing, and feature-flag data rather than page URLs.
+2 more findings not shown
Hola VPN version history
1.249.511
Mar 4, 2026
+11 more
1.259.785
Sep 30, 2026
1.260.490
Oct 13, 2026
1.261.958
Nov 4, 2026
Where Hola VPN sends data
- perr.hola.org/client_cgi/perr128 calls
From its background script · only this extension
- client-cdn4.hola.org/client_cgi/bext_config.json16 calls
From its background script · only this extension
- client.hola.org/client_cgi/get_uuid_info16 calls
From its background script · also found in its code · only this extension
- client-cdn4.hola.org/client_cgi/conn_test8 calls
From its background script · only this extension
- client.hola.org/client_cgi/fetch_info8 calls
From its background script · also found in its code · only this extension
- client.hola.org/client_cgi/is_user_geo_blocked8 calls
From its background script · also found in its code · only this extension
- client.hola.org/client_cgi/trial_get38 calls
From its background script · also found in its code · only this extension
- client.hola.org/client_cgi/unblocking_rate8 calls
From its background script · also found in its code · only this extension
- hola.org/conn_test8 calls
From its background script · only this extension
- hola.org/users/get_user8 calls
From its background script · only this extension
- hola.org/users/payment/…8 calls
From its background script · only this extension
- client.hola.org/client_cgi/background_init7 calls
From its background script · also found in its code · only this extension
- client.hola.org/client_cgi/conn_test6 calls
From its background script · also found in its code · only this extension
- perr.hola.org/client_cgi/perr/…6 calls
From its background script · only this extension
- zagent1614.hola.org/ajax_via_proxy3 calls
From its background script · only this extension
- client.hola.org/client_cgi/chrome_headers2 calls
From its background script · also found in its code · only this extension
- client.hola.org/client_cgi/rule_ratings2 calls
From its background script · also found in its code · only this extension
- zagent1614.su89-cdn.net/ajax_via_proxy2 calls
From its background script · only this extension
- zagent2712.hola.org/ajax_via_proxy2 calls
From its background script · only this extension
- zagent2013.hola.org/ajax_via_proxy1 call
From its background script · only this extension
Chrome Web Store listing
- Versions
- 1.261.958 latest of 15 seen since March 4, 2026
- Store rating
- 4.8 from 368,076 ratings
- Last updated
- April 30, 2026
- Size
- 2.11 MiB
- Privacy policy
- hola.org
