Is Bardeen: Automate Browser Apps with AI safe?
Bardeen is low risk. Code analysis shows the error reporting library attaches your email, username and ID to log entries sent to Sentry. Sentry traffic was observed, but its contents were not captured.…
Who publishes itBardeen Inc - no other listings under this identity, 1 shared hostname
Bardeen Inc - no other listings under this identity, 1 shared hostname
Shared hosts - 1 hostname
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.
Bardeen findings
Bardeen's error reporter is coded to add your email and user ID to Sentry logs
Code analysis shows the error reporting library attaches your email, username and ID to log entries sent to Sentry.
Sentry traffic was observed, but its contents were not captured.
What actually happens
A log entry or error is produced while you use the extension.
Your user ID, email and username are added to the entry before it goes to Sentry.
The code that does this
Log hook that attaches user identity
const {user:{id, email, username}, attributes = {}} = getScopeData(...);setAttr(attrs, "user.id", id);setAttr(attrs, "user.email", email);setAttr(attrs, "user.name", username);Fields the log hook can attach
- User IDusr_8f3a21c9
Ties each log entry to your account.
- Emailjane.doe@example.com
Names you directly in vendor logs.
- UsernameJane Doe
Your display name, added to the same entry.
- Page activityfetch api.prod.bardeen.ai
Clicks, requests and navigation noted as context.
Where reports are sent
- o548663.ingest.sentry.io
Sentry error and log ingest, project 5673736; one POST was observed during dynamic analysis, body not captured.
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.
Background Worker Tracks Every Tab's URL and Address-Bar Navigation
Bardeen requests <all_urls> and tracks tab creation, switch, close, navigation, focus change across your whole session, not just automated pages.
DA confirmed this live.
Full tab history is held in memory for automation; no exfil seen.
What actually happens
You navigate between pages, switch tabs, or type a URL into the address bar, anywhere on any website.
This includes ordinary browsing that has nothing to do with running an automation.
The background service worker records the full URL, transition type, and tab/window state for every tab in an in-memory session map.
Navigations typed directly into the address bar are explicitly flagged and distinguished from other transition types.
When this fires
On every browser startup
Tab, window, and navigation listeners are attached once when the background service worker starts and remain active for the whole browsing session – tracking continues on every site regardless of whether an automation is currently running.
Fields held in each tracked tab session
- Full page URLhttps://accounts.google.com/signin/v2/identifier
Every page you navigate to, including the exact URL, is captured for every open tab, not just the active one.
- Address-bar transition typetyped (from_address_bar)
The extension records whether a URL was typed directly into the address bar, reached by a reload, or reached another way.
- Tab and window stateactive: true, pinned: false, windowId: 912
Whether the tab is active, pinned, highlighted, or incognito is tracked alongside its URL.
- Tab identifier1585209824
A numeric ID ties every tracked event back to the same browser tab across its lifetime.
The code that does this
Tab/navigation listeners and per-tab session handler, shipped vs. deobfuscated
Unconditional listener registration at service-worker startup
background.js:6837-6874chrome.tabs.onActivated.addListener((...args) => { return eventQueue.push({ type: "tabs.onActivated", args });});chrome.tabs.onUpdated.addListener((...args) => { return eventQueue.push({ type: "tabs.onUpdated", args });});chrome.tabs.onRemoved.addListener((...args) => { return eventQueue.push({ type: "tabs.onRemoved", args });});chrome.tabs.onCreated.addListener((...args) => { return eventQueue.push({ type: "tabs.onCreated", args });});chrome.windows.onRemoved.addListener((...args) => { return eventQueue.push({ type: "windows.onRemoved", args });});chrome.windows.onFocusChanged.addListener((...args) => { return eventQueue.push({ type: "windows.onFocusChanged", args });});handleBrowserEvent + handleWebNavigationCommitted
background.js:7484-7536this.handleBrowserEvent = (event) => { switch (event.type) { case "tabs.onRemoved": { let [tabId] = event.args; this.untrackTab(tabId); this.uimodules.handleTabRemoved(tabId); this.emit("tab_closed", tabId); break; } case "tabs.onCreated": { let [tab] = event.args; let session = this.trackTab(tab); session && this.emit("tab_created", session.getTabItem()); break; } case "tabs.onUpdated": { let [tabId, , tab] = event.args; let session = this.tabSessions.get(tabId); if (session) { let newState = session.handleStateChange(tab); newState.active && this.emit("active_tab_change", toTabItem(newState, newState.windowId)); } else { this.trackTab(tab); tab.active && this.emit("active_tab_change", toTabItem(tab, tab.windowId)); } break; } case "tabs.onActivated": { let [{ tabId }] = event.args; let session = this.tabSessions.get(tabId); this.activeTab && this.activeTab.handleStateChange({ active: false }); if (session) { this.activeTab = session; session.handleStateChange({ active: true }); this.emit("active_tab_change", session.getTabItem()); } else { this.activeTab = null; getTab(tabId).then((tab) => { this.activeTab = this.trackTab(tab); this.emit("active_tab_change", toTabItem(tab, tab.windowId)); }, () => {}); } break; } case "webNavigation.onCommitted": { let [details] = event.args; this.handleWebNavigationCommitted(details); } }};this.handleWebNavigationCommitted = async (details) => { let { tabId, transitionType, transitionQualifiers, url } = details; if (details.frameId !== 0) return; let session = this.tabSessions.get(tabId); if (session && ((await session.getURL() === url && transitionType === "typed" && transitionQualifiers.includes("from_address_bar")) || transitionType === "reload")) { this.log.silly("Redirect detected", { tabId, url, transitionType, transitionQualifiers }); session.emit("navigate", url, url); }};What we observed, and what we didn't
Dynamic analysis confirmed the tracking machinery is live during real browsing: the background service worker issued repeated chrome.tabs.get calls immediately after each navigation, and its own "BrowserTabSession" log entries fired throughout a multi-site browsing session. We did not capture this URL/tab data being transmitted off the device in the same test session – the confirmed behavior is that the extension holds a live, full-navigation session map in the background service worker's memory, available to its automation engine, for every open tab.
Bardeen version history
4.4.0
Mar 4, 2026
4.5.0
Apr 11, 2026
5.0.0
Jun 20, 2026
5.1.0
Oct 28, 2026
Where Bardeen sends data
- bardeenmazhu.dataplane.rudderstack.com/v1/batch1 call
From its background script · only this extension
- cdn.prod.bardeen.ai/static/troubleshooting-v2.json1 call
From its background script · only this extension
- o548663.ingest.sentry.io/api/5673736/…1 call
From its background script · only this extension
Chrome Web Store listing
- Versions
- 5.1.0 latest of 4 seen since March 4, 2026
- Store rating
- 4.4 from 452 ratings
- Last updated
- June 19, 2026
- Size
- 6.77 MiB
- Privacy policy
- bardeen.ai
