Is Online Security safe?

High risk

Online Security is high risk.

Online Security reads up to 100,000 URLs from your browser history and sends them to a third-party server on every tab navigation.

On each tab switch, the extension queries the full browser history — up to 100,000 entries — and transmits the URL list as a JSON array to apis.reasonsecurity.com. A built-in allowlist of roughly 2,200 popular domains is skipped, but all other visited URLs are included in the upload. This behavior was confirmed through dynamic analysis.

ReasonLabsv7.6.0Extension ID llbcnfanfmjhpedaedhbcnpgeepdnnokChrome Web Store
80Risk
Who publishes it

Reason Labs inc. - no other listings under this identity, 2 shared hostnames

Publisher
ReasonLabs
Declared legal entity
Reason Labs inc.
Registered address
228 Park Ave S, New York, NY 10003-1502, US
Registered contact
Reason Labs inc.

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.

reasonlabs.com
Also called by 1 other listing: SafePass Password Manager
webtorrent.io
Also called by 3 other listings, including Encyclosphere, Shake Torrent
AI-assisted analysis.

Online Security findings

Code can report cross-site navigations and traffic source to a remote endpoint

HighunwantedCWE-200Static analysis

Code analysis shows it can report the target address, source site and referrer (such as Facebook or TikTok) of cross-site visits in batches, when a remote feature flag enables it.

What actually happens

You did this

You follow a link from one website to another.

For example from a social feed to an external page.

The extension did this

If the remote flag is on, the extension queues a record of the visit for upload.

The record names the target site and where the visit came from.

Fields the code assembles per navigation

  • Target address
    https://shop.example.com/offer?id=123

    The page you are navigating to.

  • Source site
    facebook.com

    The domain you came from.

  • Source type
    facebook

    Whether the visit came from a social platform or organically.

  • Source identifier
    post_8841207

    An identifier for the post or ad that was clicked.

  • Frame domain
    ads.example.net

    The embedding frame's domain, if any.

The code that does this

Flag-gated listener registration and report endpoint

Readable version

Same logic, readable

background.bundle.js
class RedirectTracker {  reportEndpoint = PROD ? 'https://extgw.mozoapi.com/protection/url' : staging;  BATCH_MAX_SIZE = 5; BATCH_MAX_WAIT_MS = 10000;  async init() {    this.enabled = await getRemoteConfig('traffic_source_protection');    if (this.enabled) this.registerListeners(); // webNavigation.onBeforeNavigate / onCommitted  }}

When this fires

When a batch threshold is hit · flushes at 5 queued events

Records are sent when five are queued or ten seconds have passed, whichever comes first.

Destination named in the code

    • extgw.mozoapi.com

    Receives the batched navigation records via POST /protection/url.

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.

Installed-extension IDs sent to a remote API that can auto-disable them

HighunwantedCWE-200Dynamic sandbox

Online Security enumerates every other installed extension, POSTs the ID list to extgw.mozoapi.com/protection/extension/scan, and disables any marked non-"ok" via chrome.management.setEnabled.

What actually happens

You did this

A scheduled scan runs (on startup, on idle, or on a recurring timer), no action from you is required.

The extension did this

The extension lists every other extension you have installed and sends all of their IDs to a remote scanning server.

For any extension the server marks as not "ok", the extension turns it off using chrome.management.setEnabled(id, false).

What is sent to the scan server, and what comes back

  • ID of every installed extension
    ["cjpalhdlnbpafiamejdnhcphjbkeiagm","gighmmpiobklfepjocnamgkkbiglidom","nkbihfbeghpgoedpieklcmphcijmoiob"]

    A complete inventory of your other installed extensions, by Chrome Web Store ID. The extension's own ID is excluded.

  • Per-extension verdict
    {"gighmmpiobklfepjocnamgkkbiglidom":{"status":"malicious"}}

    The server's response status for each ID. Anything other than "ok" causes that extension to be disabled on your machine.

The code that does this

The code that enumerates, transmits, and disables, from the shipped 7.5.0 source.

Readable version

Enumerate, POST, disable (readable)

async scanAll() {  const all = await chrome.management.getAll();  const ids = [];  const byId = new Map();  all.forEach((ext) => {    if (ext.id === chrome.runtime.id || ext.type !== 'extension') return;    ids.push(ext.id);                       // collect every other extension's ID    byId.set(ext.id, { id: ext.id, name: ext.name, permissions: ext.permissions, ... });  });  let { extensions = {} } = await chrome.storage.local.get('extensions');  const verdicts = await postScan(ids);     // POST the full ID list to the server  if (!verdicts) return extensions;  for (const [id, v] of Object.entries(verdicts)) {    const malicious = v.status !== 'ok';    // server decides    extensions[id] = { ...byId.get(id), malicious };    if (malicious && !extensions[id].whitelisted) {      await chrome.management.setEnabled(id, false);  // disable it      extensions[id].enabled = false;    }  }}

The POST to the scan API (readable)

// Ir / postScanasync function postScan(ids) {  return await httpFetch('https://extgw.mozoapi.com/protection/extension/scan', {    method: 'POST',    headers: { 'Content-Type': 'application/json' },    body: JSON.stringify(ids),            // raw array of extension IDs  });}

Where the extension inventory is sent

    • extgw.mozoapi.com

    Receives the full list of installed-extension IDs and returns per-ID verdicts. Operated by ReasonLabs/Mozo. Earlier versions used api.reasonsecurity.com.

Reproduce it yourself

Paste into the Online Security service-worker DevTools console. It wraps chrome.management.getAll, chrome.management.setEnabled, and fetch so you can watch the extension inventory being collected, the POST to the scan endpoint, and any setEnabled(false) calls that disable other extensions.

Requires
  • Chrome with Developer mode enabled
online-security-scan-inspector.js · js
// online-security-scan-inspector.js// Run in the Online Security service-worker DevTools console.(function () {  const mgmt = chrome.management;  const origGetAll = mgmt.getAll.bind(mgmt);  mgmt.getAll = async function (...a) {    const r = await origGetAll(...a);    console.log('[SCAN] chrome.management.getAll ->', r.map(e => e.id));    return r;  };  const origSetEnabled = mgmt.setEnabled.bind(mgmt);  mgmt.setEnabled = function (id, enabled, ...rest) {    console.warn('[SCAN] setEnabled', id, enabled);    return origSetEnabled(id, enabled, ...rest);  };  const origFetch = self.fetch.bind(self);  self.fetch = function (url, opts) {    if (String(url).includes('/protection/extension/scan')) {      console.log('[SCAN] POST', url, opts && opts.body);    }    return origFetch(url, opts);  };  console.log('[SCAN_INSPECTOR] installed — trigger a scan to see activity.');})();
How to run it
  1. 1Open chrome://extensions, enable Developer mode.
  2. 2Click 'service worker' under Online Security.
  3. 3Paste this script in.
  4. 4Trigger a scan (or wait) and watch the [SCAN] log lines.

Your Full Browsing History Sent to ReasonSecurity on Every Page Load

HighunwantedCWE-200Dynamic sandbox

Each time you visit a site, Online Security reads up to 100,000 URLs from your history and sends them in plain text to ReasonSecurity's servers, no consent prompt.

What actually happens

You did this

You navigate to any website not on the extension's built-in allowlist.

The allowlist covers roughly 2,200 popular domains (Google, Facebook, YouTube, etc.), leaving the vast majority of sites unprotected.

The extension did this

The extension immediately reads up to 100,000 URLs from your browser history and sends them to ReasonSecurity's servers.

The POST fires within seconds of the page loading, before you have taken any deliberate action.

What gets uploaded in every POST request

  • Visited URLs
    https://myhealth.example.com/results/blood-test-2024

    Every page you've opened in Chrome that isn't on the allowlist, including banking sites, health searches, and private browsing destinations.

  • Visit timestamp
    1712963847231

    When each URL was visited, letting the server reconstruct your browsing timeline.

  • Batch size
    99,847 URLs

    Up to 100,000 URLs sent in a single request, your entire reachable browsing history.

Captured request

POSThttps://apis.reasonsecurity.com/SSE/v1/scan/urls.ashx

200 OK, JSON object containing scan results per URL

Headers
Content-Type
application/json
Body
[  "https://news.ycombinator.com",  "https://reddit.com/r/programming",  "https://stackoverflow.com/questions/12345678",  "https://mail.proton.me/u/0/inbox",  "https://mybank.example.com/accounts"]

The code that does this

The newScan() function, reads history and POSTs to ReasonSecurity

Readable version

Annotated — newScan(urls, options)

async newScan(urls, options) {  // Load cached safe/malicious URL lists from extension storage  const { safeLinks = {}, maliciousLinks = {} } = await storage.get();  const urlStrings = urls.map(({ url }) => url);  // Build the set of already-known-malicious links to skip  let knownMalicious = {};  if (options?.last30Days) {    const cutoff = new Date();    cutoff.setDate(cutoff.getDate() - 30);    Object.keys(maliciousLinks).forEach(key => {      if (cutoff.getTime() < maliciousLinks[key].visitedAt)        knownMalicious[key] = maliciousLinks[key];    });  } else {    knownMalicious = { ...maliciousLinks };  }  // Filter: remove allowlisted and already-cached URLs  const { urlsToScan, httpProtocolUrls } =    await this.filterOutUrlsForScanning(urlStrings, knownMalicious, safeLinks);  if (urlsToScan.length > 0) {    // POST plain-text URL array to ReasonSecurity — no hashing, no encryption    const endpoint =      "https://apis.reasonsecurity.com/SSE/v1/scan/urls.ashx" +      (await featureFlag("block_page_detection") ? "?v=2" : "");    const response = await fetch(endpoint, {      method: "POST",      headers: { "Content-Type": "application/json" },      body: JSON.stringify(urlsToScan),  // raw URLs, no anonymisation    });    // ... process response  }}

Annotated — navigation trigger (fires on every page load)

webNavigation.onDOMContentLoaded.addListener(async ({ tabId, url, frameId }) => {  await this.init();  if (frameId !== 0) return;  // top-level frame only  const hostname = new URL(url).hostname;  if (/* not a listed domain */) return;  // Skip allowlisted domains (Wa = ~2,200 popular sites)  if (this.checkIfUrlIsSafe(url)) return;  const settings = await storage.get();  if (settings.realTimeScan?.sites) {    // Trigger full history upload for every non-allowlisted page load    await this.newScan([{ url: normalise(url), visitedAt: Date.now() }]);  }});

Annotated — checkIfUrlIsSafe() allowlist check

checkIfUrlIsSafe(url) {  const rootDomain  = getRootDomain(url);   // Sr()  const normalisedUrl = normalise(url);      // xr()  const { protocol } = new URL(url);  // Pass if domain is in the Wa hardcoded allowlist (~2,200 entries),  // or is localhost, or uses chrome:// scheme, or matches a built-in safe list  return !!allowlist[rootDomain]           // Wa — e.g. google.com, facebook.com    || rootDomain === "localhost"    || protocol.includes("chrome")    || Object.values(internalSafeList).includes(normalisedUrl);  // NOTE: everything else — banking, health, private pages — is NOT safe}

Where your browsing history is sent

    • apis.reasonsecurity.com

    Primary scan API operated by ReasonSecurity (the developer of Online Security). Receives plain-text URL arrays from every user's browser history on each page navigation.

+10 more findings not shown

If you have Online Security installed

  1. Open chrome://extensions and turn on Developer mode to show IDs. Find the one with ID llbcnfanfmjhpedaedhbcnpgeepdnnok and choose Remove.
  2. Block the servers only it was seen contacting: o1271931.ingest.sentry.io, extgw.mozoapi.com, ab.reasonlabsapi.com, config.reasonsecurity.com, pac.rlpaservices.com.
  3. Scan your browser to check the rest of your extensions.

What Online Security can do

Permissions this extension asks for, as declared in version 7.6.0. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.

  • Read and change your data on every site you visit

    <all_urls>

  • Store data in your browser

    storage

  • Store an unlimited amount of data in your browser

    unlimitedStorage

  • See, disable and uninstall your other extensions, including your security ones

    management

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

    tabs

  • Block and redirect the requests your browser makes

    declarativeNetRequest

  • Start, monitor and manage your downloads

    downloads

  • Open files you have downloaded

    downloads.open

  • Show you desktop notifications

    notifications

  • See every page you navigate to, as you navigate to it

    webNavigation

  • Add items to the right-click menu

    contextMenus

  • Change per-site browser settings such as cookies, JavaScript and camera access

    contentSettings

  • Clear your browsing history, cache and cookies

    browsingData

  • Read and change your full browsing history

    history

  • Talk to a program installed on your computer, outside the browser's sandbox

    nativeMessaging

  • Detect when you step away from your computer

    idle

  • Schedule its own background tasks

    alarms

  • Read and change cookies, including the ones that keep you signed in

    cookies

downloads.shelf

Online Security version history

  1. 7.4.5

    Mar 4, 2026

  2. 7.5.0

    Mar 4, 2026

  3. 7.6.0

    Jul 2, 2026

Where Online Security sends data

  • o1271931.ingest.sentry.io/api/…5 calls

    From its background script · only this extension

  • extgw.mozoapi.com/protection/url/…4 calls

    From its background script · only this extension

  • ab.reasonlabsapi.com/api/features/…3 calls

    From its background script · only this extension

  • config.reasonsecurity.com/public2 calls

    From its background script · only this extension

  • pac.rlpaservices.com2 calls

    From its background script · only this extension

  • apis.reasonsecurity.com

    Found in its code · only this extension

Chrome Web Store listing

Versions
7.6.0 latest of 3 seen since March 4, 2026
Store rating
3.6 from 591 ratings
Last updated
February 16, 2026
Size
1.49 MiB
Privacy policy
reasonlabs.com
Updated November 20, 2026