🛡️
Safe Outreach

Is FlowChat safe on LinkedIn in 2026?

No — LinkedIn detects FlowChat (we checked it ). FlowChat's extension ID is on LinkedIn's AED detection list (Nov 2026 snapshot), and LinkedIn's page code checks for FlowChat on every visit by requesting chrome-extension://eigpceijfgcoknincjhkomfodneifcnp/assets/media/manychat.png — a file that exists only if FlowChat is installed. Our automated scan of FlowChat 3.9.0.6 found code that references LinkedIn's session cookie li_at (1 matches in 1 files); whether FlowChat sends that cookie anywhere needs a manual dataflow review.

Updated · LinkedIn AED snapshot Nov 2026

ID: eigpceijfgcoknincjhkomfodneifcnp

Does LinkedIn detect FlowChat? What we found in its code

Detected by LinkedIn

This browser extension is actively compiled into LinkedIn's frontend detection lists. LinkedIn's scripts can detect when this is active on your browser.

LinkedIn requests: chrome-extension://eigpceijfgcoknincjhkomfodneifcnp/assets/media/manychat.png
DETECTED

What this means: detection isn't an instant ban — it's one input to LinkedIn's risk score. But it's a standing signal: it stacks with your behavior (volume, programmatic clicks) and device fingerprint, and this is just the AED list — one of LinkedIn's three detection systems (see how it works).

What our automated scan found in FlowChat's code

We downloaded FlowChat version 3.9.0.6 from the Chrome Web Store on and searched its 206 code files for the patterns below. Each line shows the first place we found it.

  • FlowChat's code references li_at — LinkedIn's session cookie, the one that keeps you logged in. 1 match in 1 file — first at assets/js/fc_automation_action.js:3504.
  • FlowChat's code references JSESSIONID — LinkedIn's CSRF cookie, needed to call LinkedIn's internal API as you. 11 matches in 2 files — first at assets/js/li-voyager-params.js:4.
  • FlowChat's code calls paths of LinkedIn's internal Voyager API (voyager/api). 12 matches in 2 files — first at assets/js/li-voyager-params.js:49.
  • FlowChat uses the Chrome cookies API (chrome.cookies), which reads cookies of every site it has access to. 7 matches in 2 files — first at background.js:1133.
  • FlowChat reads or writes document.cookie inside pages. 8 matches in 4 files — first at assets/js/fc_automation_action_ig.js:2125.
  • FlowChat uses the Chrome debugger API, which can drive a tab the way automation tools do. 7 matches in 1 file — first at assets/js/hidden-automation-window.js:60.
  • FlowChat creates synthetic clicks or keystrokes (dispatchEvent / MouseEvent) — LinkedIn can tell these from real input (isTrusted=false). 211 matches in 34 files — first at assets/js/enrichment-lead.js:484.
  • FlowChat runs code built at runtime (eval / new Function). 1 match in 1 file — first at assets/js/lib/jszip.min.js:13.
  • FlowChat makes its own network requests (fetch / XHR / WebSocket). 43 matches in 12 files — first at assets/js/background-login.js:311.
  • FlowChat's code mentions linkedin.com. 205 matches in 17 files — first at assets/js/enrichment-lead.js:274.
Permissions FlowChat asks for
alarmsactiveTabscriptingstoragecookiesunlimitedStoragedebuggertabsoffscreentabGroups*://*/*

What this scan is — and isn't. It is an automated static search of the shipped package, not a full teardown: a match means the pattern is in the code, not that FlowChat misuses it, and no match doesn't prove absence (minified or runtime-built code can hide it). We haven't traced where FlowChat sends data. How we test

How LinkedIn checks for FlowChat: the AED probe

That verdict isn't a guess. This is what LinkedIn's own page code does on every visit — simplified from its production bundle, which the BrowserGate investigation reverse-engineered line by line:

// LinkedIn's page bundle — simplified from BrowserGate's teardown
const hits = [];
for (const { id, file } of AED_LIST) // 4,934 ids incl. this one
try { await fetch("chrome-extension://" + id + "/" + file); hits.push(id); }
catch {} // not installed → silently swallowed
fireTrackingPayload("AedEvent", { browserExtensionIds: hits }); // → POST /li/track
// this extension is probed at:
// chrome-extension://eigpceijfgcoknincjhkomfodneifcnp/assets/media/manychat.png
On LinkedIn’s AED list
Yes
1 of 4,934 · snapshot Nov 2026
URL LinkedIn requests
chrome-extension://eigpceijfgcoknincjhkomfodneifcnp/assets/media/manychat.png
the extension's ID + a file bundled inside it
Store status
Live on the Web Store
Source
LinkedIn bundle
ℹVerify it yourself: on linkedin.com open DevTools → Sources and search the page bundle for eigpceijfgco… or AedEvent; or Network → filter li/track to watch the verdict ship. The scan runs even in Incognito. Below — the full code-level teardown.
FlowChat — marketed on the Chrome Web Store, detected by LinkedIn
Vendor's own Chrome Web Store screenshot — this extension is on LinkedIn's detection list.

How LinkedIn fingerprints your browser while you use FlowChat

Even after a cookie is copied out, LinkedIn keeps one more receipt on every request that follows — a 48-point snapshot of the exact machine making it. Faking it convincingly means reproducing that machine's quirks, not just editing a string.

Click any signal above for what it means. These are illustrative values — this demo never reads your actual device.

Your 48-point fingerprint — RSA-encrypted, attached to every API call in this session, not just login

This extension runs inside your real browser, so its requests always carry your real fingerprint — that isn't something it controls, it's simply where its code executes.

Verified against LinkedIn source-code, Nov 2026 snapshot.Read full study

Similar LinkedIn tools we checked

Same architecture and risk as FlowChat — each with its own code audit.

All extension checks