Is Findy safe on LinkedIn in 2026?

Risky — LinkedIn fingerprinted Findy (we checked it November 6, 2026), and Findy has since been removed from the Chrome Web Store (Nov 2026 snapshot). If an old copy of Findy is still installed, LinkedIn keeps detecting it on every visit. Our automated scan of Findy 3.18.25 found code that references LinkedIn's session cookie li_at (3 matches in 1 files); whether Findy sends that cookie anywhere needs a manual dataflow review.

Updated November 6, 2026 · LinkedIn AED snapshot Nov 2026

ID: amcdijdgmckgkkahhcobikllddfbfidi

Does LinkedIn detect Findy? What we found in its code

Fingerprinted & removed

LinkedIn audited this extension and fingerprinted its files in its client code. Since then, the extension has been removed or delisted from the Chrome Web Store (either by Google for policy violations, or by the developers to avoid bans).

Probed URL: chrome-extension://amcdijdgmckgkkahhcobikllddfbfidi/src/sidebar/index.html

Vulnerable

Scanning risk: If you currently have an old package of this extension active on your drive, LinkedIn continues to scan your browser using HTTP requests to its unique internal files.

What our automated scan found in Findy's code

We downloaded Findy version 3.18.25 from the Chrome Web Store on November 2, 2026 and searched its 67 code files for the patterns below. Each line shows the first place we found it.

Findy's code references li_at — LinkedIn's session cookie, the one that keeps you logged in. 3 matches in 1 file — first at assets/index.ts-68a1d56e.js:1.
Findy's code references JSESSIONID — LinkedIn's CSRF cookie, needed to call LinkedIn's internal API as you. 4 matches in 1 file — first at assets/index.ts-68a1d56e.js:1.
Findy's code calls paths of LinkedIn's internal Voyager API (voyager/api). 5 matches in 1 file — first at assets/index.ts-68a1d56e.js:1.
Findy uses the Chrome cookies API (chrome.cookies), which reads cookies of every site it has access to. 8 matches in 1 file — first at assets/index.ts-68a1d56e.js:1.
Findy reads or writes document.cookie inside pages. 5 matches in 2 files — first at assets/extension-on-installed-889aaf0d.js:3.
Findy creates synthetic clicks or keystrokes (dispatchEvent / MouseEvent) — LinkedIn can tell these from real input (isTrusted=false). 104 matches in 12 files — first at assets/cjs-c71f9d07.js:3.
Findy runs code built at runtime (eval / new Function). 4 matches in 2 files — first at assets/inboxsdk-a8f65301.js:3209.
Findy makes its own network requests (fetch / XHR / WebSocket). 68 matches in 14 files — first at assets/compose-buttons-init.js-c9cdb204.js:1.
Findy's code mentions linkedin.com. 41 matches in 7 files — first at assets/index-33b1114f.js:1.

Permissions Findy asks for

storagetabssystem.displaynotificationswebRequestwebNavigationscriptingcookiesidentityclipboardReadclipboardWritesidePanelhttps://www.linkedin.com/*/*https://mail.google.com/*https://contacts.google.com/*https://api.reply.io/*

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 Findy misuses it, and no match doesn't prove absence (minified or runtime-built code can hide it). We haven't traced where Findy sends data. How we test

How LinkedIn checks for Findy: 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://amcdijdgmckgkkahhcobikllddfbfidi/src/sidebar/index.html

On LinkedIn’s AED list

Yes

1 of 4,934 · snapshot Nov 2026

URL LinkedIn requests

chrome-extension://amcdijdgmckgkkahhcobikllddfbfidi/src/sidebar/index.html

the extension's ID + a file bundled inside it

Store status

Flagged & removed

Source

LinkedIn bundle

ℹVerify it yourself: on linkedin.com open DevTools → Sources and search the page bundle for amcdijdgmckg… or AedEvent; or Network → filter li/track to watch the verdict ship. The scan runs even in Incognito. Below — the full code-level teardown.

Findy — 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 Findy

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