Is Golos — free access to YouTube and independent multimedia. safe?

High risk

Поток is high risk. When you click the connect button, the extension fetches your public IP address from api.ipify.org and pairs it with a persistent device identifier stored on your machine, then sends both to a remote server at a domain resolved from a Google Cloud Storage config file.…

pets.toroboanv2.1.0Extension ID ocionjkjaapcailghfnhnjkpapepelibChrome Web Store
74Risk
Who publishes it

NAOBOROT LLP - 4 other listings from the same operator, none carrying a finding

Publisher
pets.toroboan
Declared legal entity
NAOBOROT LLP
Registered address
3rd Floor Suite, 207 Regent Street, London W1B 3HH, GB
Registered contact
Naoborot LLP

Same operator - 4 listings

Published under a different store account, but sharing the registered address, contact or declared legal entity this one gave the store.

Shared hosts - 2 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.

cukubst.top
Also called by 1 other listing: TwiHD
staticfiles.cukubst.top
Also called by 5 other listings
AI-assisted analysis.

Поток findings

Device ID and Public IP Transmitted to Remote Proxy API on Every Connection

HighunwantedCWE-359Dynamic sandbox

When you click the connect button, the extension fetches your public IP address from api.ipify.org and pairs it with a persistent device identifier stored on your machine, then sends both to a remote server at a domain resolved from a Google Cloud Storage config file.

What actually happens

You did this

You click the connect button in the extension popup.

The extension did this

The extension fetches your real public IP address, retrieves your persistent device ID from local storage, and sends both in a plaintext POST request to the configured proxy API.

The destination domain is not hardcoded; it is read from a remote JSON config on Google Cloud Storage each time.

Captured request

POSThttps://ptkdfjnflmpalkfpkehjgopmjldhjhgb.click/api/v1/get-proxy

Returns {host, port} used to configure chrome.proxy.settings with a PAC script pointing to the assigned proxy.

Headers
Content-Type
application/json
Body
{  "device_id": "b691591-2e2b-45f5-8a34-f3ee0f36967d",  "device_ip": "217.146.93.212",  "on_fail": null}

What the extension sends in the POST body on every connect

  • Your device ID
    b691591-2e2b-45f5-8a34-f3ee0f36967d

    A persistent identifier unique to your installation. The same ID is sent every time you connect, across all browser sessions.

  • Your public IP address
    217.146.93.212

    Your real internet-facing IP address, fetched from api.ipify.org immediately before being forwarded to the proxy server.

The code that does this

The connection function from the extension's shipping source:

Readable version

Config fetch + device ID + IP retrieval + POST

async function enableProxy({ onFail } = {}) {  try {    await setStorage({ currentState: 'connecting' });    // Step 1: get API base URL from remote config    const config = await loadConfig();    if (!config) return;    const apiBaseUrl = config.apiBaseUrl;    // Step 2: get or create persistent device ID    const { deviceId } = await getLocalStorage(StorageKey.DeviceId);    const resolvedDeviceId = deviceId ?? await (async () => {      const newId = 'xxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx'.replace(/[xy]/g, c => {        const r = Math.random() * 16 | 0;        return (c === 'x' ? r : (r & 0x3 | 0x8)).toString(16);      });      await setStorage({ deviceId: newId });      return newId;    })();    // Step 3: fetch real public IP address    const publicIp = await (async () => {      try {        const res = await fetch('https://api.ipify.org?format=json');        return (await res.json()).ip;      } catch { return null; }    })();    // Step 4: POST device_id + device_ip to the proxy API    const proxyInfo = await (async ({ apiBaseUrl, deviceId, deviceIp, onFail }) => {      const res = await fetch(`https://${apiBaseUrl}/api/v1/get-proxy`, {        method: 'POST',        headers: { 'Content-Type': 'application/json' },        body: JSON.stringify({          device_id: deviceId ?? 'unknown',          device_ip: deviceIp ?? 'unknown',          on_fail: onFail        })      });      return res.json();    })({ apiBaseUrl, deviceId: resolvedDeviceId, deviceIp: publicIp, onFail });  } catch (e) { /* ... */ }}

Where your data is sent

    • api.ipify.org

    Public IP lookup service. The extension fetches your real IP here before forwarding it to the proxy API.

    • ptkdfjnflmpalkfpkehjgopmjldhjhgb.click

    Proxy API endpoint that receives your device ID and public IP. The domain is resolved at runtime from a remote config file; it can change without an extension update.

A settings file on storage.googleapis.com decides where your device ID and IP go

HighunwantedCWE-829Dynamic sandbox

At every startup the extension fetches a settings file from storage.googleapis.com whose server address decides where your device ID and IP are sent on connect.

What actually happens

You did this

You open your browser with the extension installed.

The extension did this

The extension fetches a JSON config from Google Cloud Storage and reads apiBaseUrl. Later requests carrying your device ID and public IP go to the domain named there.

The config can change at any time without an extension update, any domain can be placed in apiBaseUrl.

Captured request

GEThttps://storage.googleapis.com/potok/potok.json

Returns JSON: {"apiBaseUrl": "ptkdfjnflmpalkfpkehjgopmjldhjhgb.click"}. The value of apiBaseUrl becomes the target host for all device_id and device_ip submissions.

The code that does this

Config-loading code from the extension's shipping source:

Readable version

Config loader

// Loads the remote configuration. Returns cached session copy if available.async function loadConfig() {  try {    // Check session storage cache first    const { extensionData } = await chrome.storage.session.get('extensionData');    if (extensionData !== undefined) return extensionData;    // Fetch from Google Cloud Storage — no SRI, no domain validation    const response = await fetch('https://storage.googleapis.com/potok/potok.json');    return await response.json();    // Returned object contains: { apiBaseUrl: "<hostname>" }    // This hostname is used directly for the POST /api/v1/get-proxy call  } catch (e) {    console.error('Error loading configuration:', e);    await chrome.storage.local.set({ currentState: 'error' });  }}

What a config change means for you

Because the API base URL is fetched fresh from storage.googleapis.com/potok/potok.json on every browser startup, the owner of that file can point the data recipient to any domain at any time. Users receive no notification when this changes. The extension does not validate the returned domain against any allowlist, and there is no Subresource Integrity (SRI) check on the fetched JSON.

Hosts involved in the remote config chain

    • storage.googleapis.com

    Google Cloud Storage bucket 'potok' serving the runtime config file potok.json. Controls the destination for all device data.

    • ptkdfjnflmpalkfpkehjgopmjldhjhgb.click

    Proxy API endpoint resolved from potok.json at the time of our test session. Received POST requests with device_id and device_ip.

YouTube traffic routes through service-provided proxies

MediumunwantedCWE-200Dynamic sandbox

Turning the YouTube accelerator on has the extension ask its service for a proxy host/port, then install a rule routing YouTube, googlevideo, ytimg, ggpht traffic through it.

What actually happens

You did this

You press the extension's main button to connect the YouTube accelerator.

The popup writes the connected target state when the connection timer still allows a session.

The extension did this

The service worker requests proxy details and configures Chrome to route YouTube-related traffic through the returned proxy.

The PAC script exempts music.youtube.com but routes googlevideo.com, youtube.com, ytimg.com, and ggpht.com.

Captured request

POSThttps://ptkdfjnflmpalkfpkehjgopmjldhjhgb.click/api/v1/get-proxy

Dynamic analysis observed this proxy-lookup request returning proxy server details with a host and port.

Headers
Content-Type
application/json

Traffic the PAC script sends through the returned proxy

  • YouTube pages
    https://www.youtube.com/watch?v=dQw4w9WgXcQ (illustrative)

    Your YouTube page visits sit on the proxy path once connected, revealing which host you reach; visibility depends on proxy/TLS handling.

  • Video stream requests
    https://rr3---sn-n8v7zn7s.googlevideo.com/videoplayback?id=o-AJirM2F6x9 (illustrative)

    Video playback connects through googlevideo.com hosts YouTube selects; those connections can show streaming is happening through the proxy.

  • Thumbnail and image hosts
    https://i.ytimg.com/vi/dQw4w9WgXcQ/hqdefault.jpg (illustrative)

    Your YouTube image and thumbnail loads are also matched by the proxy rule, adding more page-view context to the proxy path.

  • Music YouTube exception
    https://music.youtube.com/watch?v=dQw4w9WgXcQ (illustrative)

    Music YouTube traffic is excluded from the proxy rule, so routing targets only other YouTube-related hosts named in the PAC script.

The code that does this

The service worker fetches a proxy and installs a YouTube PAC rule

Readable version

Readable service-worker proxy workflow

background/service_worker.js
    async function b() {      try {        const {          extensionData: e        } = await y(w.ExtensionData);        if (void 0 !== e) return e;        const t = await fetch("https://storage.googleapis.com/potok/potok.json");        return await t.json()      } catch (e) {        console.error("Error loading configuration:", e), await m({          currentState: "error"        })      }    }    async function v({      onFail: e    } = {}) {      try {        await m({          currentState: "connecting"        });        const t = await b();        if (!t) return;        const n = t.apiBaseUrl,          r = await async function() {            const {              deviceId: e            } = await f(p.DeviceId);            return e || await async function() {              const e = "xxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx".replace(/[xy]/g, (e => {                const t = 16 * Math.random() | 0;                return ("x" === e ? t : 3 & t | 8).toString(16)              }));              return await m({                deviceId: e              }), e            }()          }();        r || console.warn("enableProxy: Failed to retrieve device ID, proceeding without it.");        const o = await async function() {          try {            const e = await fetch("https://api.ipify.org?format=json");            return (await e.json()).ip          } catch (e) {            return console.error("Error fetching public IP:", e), null          }        }();        null === o && console.warn("enableProxy: Failed to retrieve public IP address, proceeding without it.");        const i = await async function({          apiBaseUrl: e,          deviceId: t,          deviceIp: n,          onFail: r        }) {          const o = await fetch(`https://${e}/api/v1/get-proxy`, {            method: "POST",            headers: {              "Content-Type": "application/json"            },            body: JSON.stringify({              device_id: t ?? "unknown",              device_ip: n ?? "unknown",              on_fail: r            })          });          return await o.json()        }({          apiBaseUrl: n,          deviceId: r,          deviceIp: o,          onFail: e        }), {          host: a,          port: s        } = i;        chrome.proxy.settings.set({          value: {            mode: "pac_script",            pacScript: {              data: `\n              function FindProxyForURL(url, host) {\n                  if (dnsDomainIs(host, ".music.youtube.com")) {\n                    return "DIRECT";\n                  }\n\n                  if (dnsDomainIs(host, ".googlevideo.com") ||\n                      dnsDomainIs(host, ".youtube.com") ||\n                      dnsDomainIs(host, ".ytimg.com") ||\n                      dnsDomainIs(host, ".ggpht.com")) {\n                      return "PROXY ${a}:${s}";\n                  }\n                  return "DIRECT";\n              }\n            `            }          },          scope: "regular"        }, (async () => {          if (chrome.runtime.lastError) await m({            currentState: "error"          }), console.error("Error setting proxy:", chrome.runtime.lastError.message);          else {            const {              connectionCount: e,              targetState: t            } = await f([p.ConnectionCount, p.TargetState]), n = e ?? 0;            "disconnected" === t ? S() : await m({              currentState: "connected",              connectionCount: n + 1            })          }        }))      } catch (e) {        console.error("Error loading configuration:", e), await m({          currentState: "error"        })      }    }

External services involved before the PAC rule is installed

    • storage.googleapis.com

    Hosts the potok.json configuration that names the extension service domain.

    • ptkdfjnflmpalkfpkehjgopmjldhjhgb.click

    Receives the proxy-lookup POST and returns the proxy host and port used by the PAC script.

    • api.ipify.org

    Receives a public-IP lookup before the proxy-selection request is made.

+1 more finding not shown

If you have Поток installed

  1. Open chrome://extensions and turn on Developer mode to show IDs. Find the one with ID ocionjkjaapcailghfnhnjkpapepelib and choose Remove.
  2. Scan your browser to check the rest of your extensions.

What Поток can do

Permissions this extension asks for, as declared in version 1.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 2.1.0, which we have not unpacked yet.

  • Read and change your data on youtube.com

    https://*.youtube.com/*

  • Route all of your browsing through a server of its choosing

    proxy

  • Store data in your browser

    storage

  • Watch every request your browser makes

    webRequest

  • Act on the current tab, but only after you click the extension

    activeTab

  • See the address and title of every tab you have open

    tabs

Поток version history

  1. 1.1.1

    Mar 4, 2026

  2. 2.0.5

    Aug 8, 2026

  3. 2.0.6

    Oct 14, 2026

  4. 2.1.0

    Nov 11, 2026

Where Поток sends data

  • storage.googleapis.com/golosapp/features.json3 calls

    From its background script · 16 other extensions

  • storage.googleapis.com/golosapp/golosapp.json2 calls

    From its background script · 16 other extensions

Chrome Web Store listing

Versions
2.1.0 latest of 4 seen since March 4, 2026
Store rating
3.7 from 5,244 ratings
Last updated
November 11, 2026
Size
616 KiB
Privacy policy
telegra.ph
Updated November 20, 2026