--- title: "Is Inven safe on LinkedIn in 2026?" description: "Does LinkedIn detect Inven? It's on LinkedIn's active detection list. Checked against LinkedIn's own 4,934-extension list — see the verdict, the probe fil…" url: https://safe-outreach.com/is-inven-safe date_published: 2026-11-08T08:01:29.733Z date_modified: 2026-11-08T00:00:00.000Z publisher: Safe Outreach --- # Is Inven safe on LinkedIn in 2026? **No — LinkedIn detects Inven** (we checked it November 8, 2026). Inven's extension ID is on LinkedIn's AED detection list (Nov 2026 snapshot), and LinkedIn's page code checks for Inven on every visit by requesting chrome-extension://bhffkcapkoknegngnbipdpiocggfkdap/inven.png — a file that exists only if Inven is installed. Our automated scan of Inven 2.4.4 found code that references LinkedIn's session cookie li\_at (2 matches in 2 files); whether Inven sends that cookie anywhere needs a manual dataflow review. Updated November 8, 2026 · LinkedIn AED snapshot Nov 2026 ID: bhffkcapkoknegngnbipdpiocggfkdap ## Does LinkedIn detect Inven? 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://bhffkcapkoknegngnbipdpiocggfkdap/inven.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](https://browsergate.eu/how-it-works/)). ### What our automated scan found in Inven's code We downloaded Inven version 2.4.4 from the Chrome Web Store on November 2, 2026 and searched its 19,443 code files for the patterns below. Each line shows the first place we found it. - Inven's code references `li_at` — LinkedIn's session cookie, the one that keeps you logged in. 2 matches in 2 files — first at dist/background.js:2. - Inven's code references `JSESSIONID` — LinkedIn's CSRF cookie, needed to call LinkedIn's internal API as you. 4 matches in 3 files — first at dist/background.js:2. - Inven's code calls paths of LinkedIn's internal Voyager API (`voyager/api`). 1 match in 1 file — first at dist/main.js:2. - Inven uses the Chrome cookies API (`chrome.cookies`), which reads cookies of every site it has access to. 4 matches in 2 files — first at dist/background.js:2. - Inven reads or writes `document.cookie` inside pages. 20 matches in 8 files — first at dist/background.js:2. - Inven creates synthetic clicks or keystrokes (`dispatchEvent` / `MouseEvent`) — LinkedIn can tell these from real input (`isTrusted=false`). 92 matches in 42 files — first at dist/main.js:2. - Inven runs code built at runtime (`eval` / `new Function`). 59 matches in 43 files — first at dist/background.js:2. - Inven makes its own network requests (`fetch` / XHR / WebSocket). 584 matches in 76 files — first at dist/background.js:2. - Inven's code mentions linkedin.com. 15 matches in 5 files — first at dist/background.js:2. Permissions Inven asks for cookies storage tabs sidePanel https://www.linkedin.com/\* https://cognito-idp.eu-north-1.amazonaws.com/\* https://app.inven.ai/\* https://api.inven.ai/\* http://localhost:5000/\* https://api.maptiler.com/\* **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 Inven misuses it, and no match doesn't prove absence (minified or runtime-built code can hide it). We haven't traced where Inven sends data. [How we test](https://safe-outreach.com/how-we-test) ### How LinkedIn checks for Inven: 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](https://browsergate.eu/how-it-works/) 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://bhffkcapkoknegngnbipdpiocggfkdap/inven.png On LinkedIn’s AED list Yes 1 of 4,934 · snapshot Nov 2026 URL LinkedIn requests chrome-extension://bhffkcapkoknegngnbipdpiocggfkdap/inven.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 bhffkcapkokn… or AedEvent; or Network → filter li/track to watch the verdict ship. The scan runs even in Incognito. Below — the full code-level teardown. ![Inven — marketed on the Chrome Web Store, detected by LinkedIn](https://storage.googleapis.com/linkedhelper-sot/checker/shots/bhffkcapkoknegngnbipdpiocggfkdap.webp) Vendor's own Chrome Web Store screenshot — this extension is on LinkedIn's detection list. ## How LinkedIn fingerprints your browser while you use Inven 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](https://safe-outreach.com/how-we-test) ## Similar LinkedIn tools we checked Same architecture and risk as Inven — each with its own code audit. - [Is ContactBook safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-contactbook-safe) - [Is Coral Starfish for Invenias safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-coral-starfish-safe) - [Is Post Formatter safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-post-formatter-linkedin-bold-text-more-styles-safe) - [Is Wiza safe on LinkedIn? uploads session HIGH](https://safe-outreach.com/is-wiza-safe) - [Is RiteTag safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-ritetag-safe) - [Is GetProspect v7.0.5 safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-getprospect-safe) [All extension checks](https://safe-outreach.com/deep-dives#all-checks) --- Source: https://safe-outreach.com/is-inven-safe