Is Toggle Extension safe?

Medium risk

Toggle is medium risk. Code analysis shows the extension listens for clicks, focus, typing and form submits on all sites, queues the field values and page URLs, and posts them to toggle.pro once signed in.

aleksandar.yordanovv2.0.0Extension ID bnkekngmddejlfdeefjilpfdhomeomgbChrome Web Store
51Risk
Who publishes it

JIVE LTD - 3 other listings from the same operator, 1 of them carrying a finding

Publisher
aleksandar.yordanov
Declared legal entity
JIVE LTD
Registered address
Petko Karavelov 9 floor 2 apartment 214, VARNA 9000, BG
Registered contact
Aleksandar JIVE LTD

Same store account

3 other listings published from this account, 1k+ users between them. 1 of them carries a finding.

AI-assisted analysis.

Toggle findings

Toggle sends clicks, field values and page URLs on all sites to toggle.pro

HighunwantedCWE-359Static analysis

Code analysis shows the extension listens for clicks, focus, typing and form submits on all sites, queues the field values and page URLs, and posts them to toggle.pro once signed in.

What actually happens

You did this

You click, focus or type in a field on any website.

The extension did this

The extension records the element, its current value, surrounding HTML and the page address, and passes it to its background worker.

Fields built for each captured event

  • Field value
    jane.doe@example.com

    The current text in the field you interacted with.

  • Page address
    https://example.com/login?next=/account

    Full URL of the page where the event happened.

  • Element HTML
    <input type="email" name="email">

    Cleaned HTML of the element plus parent and sibling context.

  • Event type
    Input input

    Which action triggered the record.

  • Device ID
    visitorId cookie value

    A fingerprint identifier added when the batch is sent.

The code that does this

Event record built in the content script

Readable version

sendEventToBackend

content.js
const eventData = {  eventType: type,  elementTag: element.tagName || "N/A",  elementId: element.id || "N/A",  elementValue: element.value || "",  exactElementHTML: getCleanedHTML(element),  elementHTMLScope: removeEmptyTags(getImmediateContext(element)),  pageURL: window.location.href,  timestamp: Date.now(),};chrome.runtime.sendMessage({ type: "eventData", eventData });

When this fires

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

Events are buffered in local storage and posted when 60 are queued or the configured sending interval has elapsed, checked by a one-minute alarm.

Destination of the queued events

    • toggle.pro

    Ingestion API receiving gzip event batches with user ID, device ID and extension version.

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.

What Toggle can do

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

    *://toggle.pro/*

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

    cookies

  • Schedule its own background tasks

    alarms

  • Store data in your browser

    storage

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

    tabs

Where Toggle sends data

  • toggle.pro/api/auth/…2 calls

    From its background script · only this extension

Chrome Web Store listing

Versions
2.0.0 seen since March 4, 2026
Store rating
3.5 from 109 ratings
Last updated
November 30, 2024
Size
7.5 MiB
Privacy policy
toggle.pro
Updated July 21, 2026