--- title: "Is Vaam safe on LinkedIn in 2026?" description: "Does LinkedIn detect Vaam? It's on LinkedIn's active detection list. Checked against LinkedIn's own 4,934-extension list — see the verdict, the probe file…" url: https://safe-outreach.com/is-vaam-safe date_published: 2026-11-06T08:01:44.726Z date_modified: 2026-11-06T00:00:00.000Z publisher: Safe Outreach --- # Is Vaam safe on LinkedIn in 2026? **No — LinkedIn detects Vaam** (we checked it November 6, 2026). Vaam's extension ID is on LinkedIn's AED detection list (Nov 2026 snapshot), and LinkedIn's page code checks for Vaam on every visit by requesting chrome-extension://mfnihmhpikbpioclaalnljadjbmbcppo/assets/selfieSegmentation/selfie\_segmentation\_solution\_simd\_wasm\_bin.data — a file that exists only if Vaam is installed. Our automated scan of Vaam 2.22.0 found code that references LinkedIn's session cookie li\_at (2 matches in 1 files); whether Vaam sends that cookie anywhere needs a manual dataflow review. Updated November 6, 2026 · LinkedIn AED snapshot Nov 2026 ID: mfnihmhpikbpioclaalnljadjbmbcppo ## Does LinkedIn detect Vaam? 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://mfnihmhpikbpioclaalnljadjbmbcppo/assets/selfieSegmentation/selfie\_segmentation\_solution\_simd\_wasm\_bin.data** 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 Vaam's code We downloaded Vaam version 2.22.0 from the Chrome Web Store on November 2, 2026 and searched its 21 code files for the patterns below. Each line shows the first place we found it. - Vaam's code references `li_at` — LinkedIn's session cookie, the one that keeps you logged in. 2 matches in 1 file — first at static/background/index.js:4131. - Vaam's code references `JSESSIONID` — LinkedIn's CSRF cookie, needed to call LinkedIn's internal API as you. 3 matches in 1 file — first at static/background/index.js:4131. - Vaam's code calls paths of LinkedIn's internal Voyager API (`voyager/api`). 21 matches in 3 files — first at linkedin.744d02ee.js:4148. - Vaam uses the Chrome cookies API (`chrome.cookies`), which reads cookies of every site it has access to. 6 matches in 6 files — first at linkedin.744d02ee.js:4167. - Vaam reads or writes `document.cookie` inside pages. 29 matches in 8 files — first at linkedin.744d02ee.js:514. - Vaam creates synthetic clicks or keystrokes (`dispatchEvent` / `MouseEvent`) — LinkedIn can tell these from real input (`isTrusted=false`). 75 matches in 8 files — first at linkedin.744d02ee.js:9. - Vaam makes its own network requests (`fetch` / XHR / WebSocket). 163 matches in 11 files — first at linkedin.744d02ee.js:17. - Vaam's code mentions linkedin.com. 103 matches in 7 files — first at linkedin.744d02ee.js:17. Permissions Vaam asks for activeTab cookies desktopCapture tabCapture storage tabs https://\*/\* **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 Vaam misuses it, and no match doesn't prove absence (minified or runtime-built code can hide it). We haven't traced where Vaam sends data. [How we test](https://safe-outreach.com/how-we-test) ### How LinkedIn checks for Vaam: 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://mfnihmhpikbpioclaalnljadjbmbcppo/assets/selfieSegmentation/selfie\_segmentation\_solution\_simd\_wasm\_bin.data On LinkedIn’s AED list Yes 1 of 4,934 · snapshot Nov 2026 URL LinkedIn requests chrome-extension://mfnihmhpikbpioclaalnljadjbmbcppo/assets/selfieSegmentation/selfie\_segmentation\_solution\_simd\_wasm\_bin.data 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 mfnihmhpikbp… or AedEvent; or Network → filter li/track to watch the verdict ship. The scan runs even in Incognito. Below — the full code-level teardown. ![Vaam — marketed on the Chrome Web Store, detected by LinkedIn](https://storage.googleapis.com/linkedhelper-sot/checker/shots/mfnihmhpikbpioclaalnljadjbmbcppo.webp) Vendor's own Chrome Web Store screenshot — this extension is on LinkedIn's detection list. ## How LinkedIn fingerprints your browser while you use Vaam 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 Vaam — each with its own code audit. - [Is XING Transfer to LinkedIn safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-xing-transfer-to-linkedin-safe) - [Is AuthoredUp safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-authoredup-safe) - [Is Creator Match safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-creator-match-grow-monetize-on-linkedin-safe) - [Is VPN для LinkedIn safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-vpn-linkedin-safe) - [Is Jobalytics safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-jobalytics-safe) - [Is FinalScout safe on LinkedIn? uploads session HIGH](https://safe-outreach.com/is-finalscout-safe) [All extension checks](https://safe-outreach.com/deep-dives#all-checks) --- Source: https://safe-outreach.com/is-vaam-safe