Is Scribe: AI Documentation, SOPs & Process Intelligence safe?

Medium risk

Scribe is medium risk. When the extension starts, it creates an offscreen document to run the LaunchDarkly SDK. DA observed startup requests, including a GET whose decoded context held an anonymous device key, then analytics and feature-flag traffic.…

chrome-store-adminsv104.39.0Extension ID okfkdaglfjjjfefdcppliegebpoegaiiChrome Web Store
55Risk
Who publishes it

Colony Labs, Inc. - no other listings under this identity

Publisher
chrome-store-admins
Declared legal entity
Colony Labs, Inc.
Registered address
427 Brannan St, San Francisco, CA 94107-1715, US
Registered contact
dba Scribe
AI-assisted analysis.

Scribe findings

LaunchDarkly Receives Extension Device Context

MediumunwantedCWE-200Dynamic sandbox

When the extension starts, it creates an offscreen document to run the LaunchDarkly SDK.

What actually happens

You did this

The extension starts after installation or browser startup.

The extension did this

It loads LaunchDarkly in an offscreen document and sends an anonymous device context to LaunchDarkly.

Captured request

GEThttps://clientsdk.launchdarkly.com/sdk/evalx/61831e1e3e135e62b5cbb6bd/contexts/eyJrZXkiOiI0NDg2ZDAxMi01ZGYzLTQyMzktYWFlNC1mZjhhYjk4YTJhNmQiLCJhbm9ueW1vdXMiOnRydWUsImtpbmQiOiJkZXZpY2UifQ

Feature-flag evaluation request; no request body because the context is encoded in the URL.

Context observed in LaunchDarkly traffic

  • Device key
    4486d012-5df3-4239-aae4-ff8ab98a2a6d

    This lets the feature-flag service associate requests with this browser's extension install.

  • Context kind
    device

    This marks the request as an anonymous device context rather than a named account.

  • Client-side ID
    61831e1e3e135e62b5cbb6bd

    This identifies the LaunchDarkly project used by the extension.

The code that does this

Offscreen LaunchDarkly setup and context construction

Readable version

Readable offscreen document creation

assets/launchdarkly-DljPGdGt.js
async function ne(e = "src/offscreen/offscreen.html") {  if (l) {    await l;    return  }  const o = chrome.runtime.getURL(e);  l = (async () => {    if (chrome.runtime.getContexts && (await chrome.runtime.getContexts({        contextTypes: ["OFFSCREEN_DOCUMENT"],        documentUrls: [o]      })).length) return;    const a = ce();    try {      await chrome.offscreen.createDocument({        url: e,        reasons: ["LOCAL_STORAGE"],        justification: "Run LaunchDarkly browser SDK in a window context; it caches flags in localStorage and requires browser-only APIs not available in the MV3 service worker."      })    } catch (m) {      const i = m instanceof Error ? m.message : String(m);      if (!/single offscreen document/i.test(i)) throw a.cancel(), m    }    await a.promise  })().catch(a => {    throw A(), a  }), await l}

Readable device context and LD_INIT call

assets/launchdarkly-DljPGdGt.js
M = async () => {  let e = await T(O);  return e || (e = await T(Q) || V(), X(O, e), e)}, P = async e => {  const o = f(),    a = {      kind: "multi",      device: {        key: await M(),        ...o ? {          extension_version: o        } : {}      }    },    m = e?.active_organization?.super_organization;  if (e) {    const i = e,      t = {        key: e.id,        email: e.email,        signupMethod: e.signup_method,        signupSource: i.signup_source,        dateJoinedTimestamp: e.date_joined ? new Date(e.date_joined).valueOf() : void 0,        businessEmail: e.email ? ie(e.email) : void 0,        roleCode: m?.role?.code      };    a.user = t  }  if (m?.id) {    const i = {      key: m.id,      plan: m.plan?.name,      proPlanType: m.pro_plan_type,      enterprisePlanType: m.enterprise_plan_type,      subscriptionStatus: m.stripe_subscription_status,      spsEnabled: m.smart_privacy_screen_enabled,      organization_id: e?.active_organization?.id,      userCount: e?.active_organization?.user_count,      createdTimestamp: m.created ? new Date(m.created).valueOf() : void 0    };    a.super_organization = i  }  if (e?.active_organization?.id) {    const i = e.active_organization,      t = i.created,      c = {        key: i.id,        ...i.name && {          name: i.name        },        created_timestamp: t ? new Date(t).valueOf() : void 0      };    a.organization = c  }  return a}, I = async () => {  try {    return await p("LD_INIT", {      clientSideId: H,      context: await P(null)    }) === !0  } catch {    return !1  }}, $ = async () => u ? !0 : s || (s = (async () => {  try {    if (await I()) return u = !0, !0;    try {      w("launchdarkly_init_failed_retrying")    } catch {}    if (await new Promise(e => {        setTimeout(e, le)      }), await I()) return u = !0, !0;    try {      w("launchdarkly_init_failed")    } catch {}    return !1  } finally {    s = null  }})(), s);

LaunchDarkly endpoints observed or configured

    • clientsdk.launchdarkly.com

    LaunchDarkly feature-flag evaluation endpoint receiving the encoded device context.

    • clientstream.launchdarkly.com

    LaunchDarkly streaming endpoint for live feature-flag updates.

    • events.launchdarkly.com

    LaunchDarkly event endpoint for diagnostic and bulk analytics events.

Scribe code can send visited page addresses with user and org IDs to its backend

MediumunwantedCWE-200Static analysis

Code analysis shows the extension can send each page address you interact with, plus your user and organisation IDs, to cortex.scribehow.com when a server-side flag is on.

What actually happens

You did this

You click or type on any page while signed in to the extension.

The extension did this

The page address (query and hash removed) and your user and organisation IDs are queued for cortex.scribehow.com.

The code that does this

Content script builds the streamed record

Readable version
const record = {  url: stripQueryAndHash(window.location.href),  timestamp: Date.now(),  user_id: user.user_id,  active_org_id: user.active_org_id,  super_org_id: user.super_org_id};chrome.runtime.sendMessage({ messageType: "stream_url_data", data: record });

The code that does this

Worker posts the batch to the stream_url endpoint

Readable version
const endpoint = `${apiBase}/api/v1/long_recorder/actions/stream_url`;const body = {  metadata: { url_count: n, batch_timestamp: Date.now() },  urls: entries.map(e => ({ url: e.url, timestamp: iso(e.timestamp), user_id: e.user_id, active_org_id: e.active_org_id }))};

Fields in each streamed entry

  • url
    https://example.com/account/settings (illustrative)

    The page address you were on, with query and hash removed.

  • user_id
    u_8f31c2a9 (illustrative)

    Your Scribe account identifier.

  • active_org_id
    org_41b7d0 (illustrative)

    The organisation your account is currently using.

  • timestamp
    2026-11-12T09:14:03.221Z (illustrative)

    When the interaction happened.

Destination

    • cortex.scribehow.com

    Receives batched page addresses with user and organisation IDs at the stream_url endpoint.

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.

Scribe added LaunchDarkly flags SDK that sends user and org context offscreen

MediumunwantedCWE-200Static analysis

Code analysis shows a background page runs the LaunchDarkly SDK and sends your user and organisation details to LaunchDarkly servers, alongside the Flagsmith service already used.

What actually happens

You did this

The extension starts and needs feature flags.

The extension did this

It opens a background page that runs LaunchDarkly's SDK, which sends your user and organisation details to LaunchDarkly.

The code that does this

Offscreen document hosts the SDK

Readable version

Offscreen document creation

assets/index.js-BCl7oekz.js
await chrome.offscreen.createDocument({  url: e,  reasons: ["LOCAL_STORAGE"],  justification: "Run LaunchDarkly browser SDK in a window context; it caches flags in localStorage and requires browser-only APIs not available in the MV3 service worker."})

SDK endpoints

assets/offscreen-DOn264j0.js
W.DEFAULT_EVENTS = "https://events.launchdarkly.com";he = "https://clientsdk.launchdarkly.com",ce = "https://clientstream.launchdarkly.com";

LaunchDarkly hosts contacted by the SDK

    • clientsdk.launchdarkly.com

    Receives user and org context; returns flag values.

    • clientstream.launchdarkly.com

    Streams flag changes to the extension.

    • events.launchdarkly.com

    Receives flag evaluation events.

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.

+2 more findings not shown

What Scribe can do

Permissions this extension asks for, as declared in version 104.39.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>

  • Schedule its own background tasks

    alarms

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

    cookies

  • Run hidden pages in the background

    offscreen

  • Run its own code inside the pages you visit

    scripting

  • Show a panel beside the page

    sidePanel

  • Store data in your browser

    storage

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

    tabs

Scribe version history

  1. 2.78.2

    Mar 4, 2026

  2. +28 more

  3. 104.37.1

    Nov 3, 2026

  4. 104.38.0

    Nov 12, 2026

  5. 104.39.0

    Nov 18, 2026

Where Scribe sends data

  • usage.scribehow.com/track24 calls

    From its background script · only this extension

  • usage.scribehow.com/engage12 calls

    From its background script · only this extension

  • scribe-api.scribehow.com/api/users/…8 calls

    From its background script · only this extension

  • api.ipify.org5 calls

    From its background script · 15 other extensions

  • api.assemblyai.com4 calls

    From its background script · only this extension

  • colony-recorder.s3-accelerate.amazonaws.com/connection-check.txt4 calls

    From its background script · only this extension

  • otel.scribehow.com/v1/logs4 calls

    From its background script · only this extension

  • otel.scribehow.com/v1/traces4 calls

    From its background script · only this extension

  • scribe-api.scribehow.com/api/users4 calls

    From its background script · only this extension

  • scribe-api.scribehow.com/health_check4 calls

    From its background script · only this extension

  • colony-labs-public.s3.us-east-2.amazonaws.com/test.json3 calls

    From its background script · only this extension

  • scribe-api.scribehow.com/api/search/…3 calls

    From its background script · only this extension

  • scribe-api.scribehow.com/api/workspace/…3 calls

    From its background script · only this extension

  • scribe-api.scribehow.com/api/track/…2 calls

    From its background script · only this extension

  • edge.api.flagsmith.com/api/v1/…1 call

    From its background script · only this extension

  • scribe-api.scribehow.com/api/app_tag/…1 call

    From its background script · only this extension

  • t1.gstatic.com/faviconV21 call

    From its own pages · 31 other extensions

Chrome Web Store listing

Versions
104.39.0 latest of 32 seen since March 4, 2026
Store rating
4.4 from 835 ratings
Last updated
November 18, 2026
Size
1.92 MiB
Privacy policy
scribe.com
Updated November 20, 2026