--- title: "Is LinkedIn Targeted Feed, Engage & Follow-Ups safe on LinkedIn in 2026?" description: "Does LinkedIn detect LinkedIn Targeted Feed, Engage & Follow-Ups? It's on LinkedIn's active detection list. Checked against LinkedIn's own 4,934-extension…" url: https://safe-outreach.com/is-linkedin-targeted-feed-safe date_published: 2026-11-14T08:00:11.577Z date_modified: 2026-11-14T00:00:00.000Z publisher: Safe Outreach --- # Is LinkedIn Targeted Feed, Engage & Follow-Ups safe on LinkedIn in 2026? **No — LinkedIn detects LinkedIn Targeted Feed, Engage & Follow-Ups** (we checked it November 14, 2026). LinkedIn Targeted Feed, Engage & Follow-Ups's extension ID is on LinkedIn's AED detection list (Nov 2026 snapshot), and LinkedIn's page code checks for LinkedIn Targeted Feed, Engage & Follow-Ups on every visit by requesting chrome-extension://mnjjmehgakbgcgoeaahodkcdlidcjnjm/icons/icon16.png — a file that exists only if LinkedIn Targeted Feed, Engage & Follow-Ups is installed. Our automated scan of LinkedIn Targeted Feed, Engage & Follow-Ups 1.0.66 found code that references LinkedIn's session cookie li\_at (6 matches in 5 files); whether LinkedIn Targeted Feed, Engage & Follow-Ups sends that cookie anywhere needs a manual dataflow review. Updated November 14, 2026 · LinkedIn AED snapshot Nov 2026 ID: mnjjmehgakbgcgoeaahodkcdlidcjnjm ## Does LinkedIn detect LinkedIn Targeted Feed, Engage & Follow-Ups? 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://mnjjmehgakbgcgoeaahodkcdlidcjnjm/icons/icon16.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 LinkedIn Targeted Feed, Engage & Follow-Ups's code We downloaded LinkedIn Targeted Feed, Engage & Follow-Ups version 1.0.66 from the Chrome Web Store on November 2, 2026 and searched its 16 code files for the patterns below. Each line shows the first place we found it. - LinkedIn Targeted Feed, Engage & Follow-Ups's code references `li_at` — LinkedIn's session cookie, the one that keeps you logged in. 6 matches in 5 files — first at assets/src/entries/facebookContent.bundle.js:8816. - LinkedIn Targeted Feed, Engage & Follow-Ups's code references `JSESSIONID` — LinkedIn's CSRF cookie, needed to call LinkedIn's internal API as you. 8 matches in 6 files — first at assets/src/entries/background/main-BA\_IfVAn.js:277. - LinkedIn Targeted Feed, Engage & Follow-Ups's code calls paths of LinkedIn's internal Voyager API (`voyager/api`). 47 matches in 8 files — first at assets/linkedinContentSearch-B4ebG93n.js:6234. - LinkedIn Targeted Feed, Engage & Follow-Ups reads or writes `document.cookie` inside pages. 14 matches in 6 files — first at assets/src/entries/background/main-BA\_IfVAn.js:277. - LinkedIn Targeted Feed, Engage & Follow-Ups creates synthetic clicks or keystrokes (`dispatchEvent` / `MouseEvent`) — LinkedIn can tell these from real input (`isTrusted=false`). 270 matches in 7 files — first at assets/GrowthGuidePage-pv4tMz01.js:1606. - LinkedIn Targeted Feed, Engage & Follow-Ups makes its own network requests (`fetch` / XHR / WebSocket). 37 matches in 9 files — first at assets/GrowthGuidePage-pv4tMz01.js:9347. - LinkedIn Targeted Feed, Engage & Follow-Ups's code mentions linkedin.com. 207 matches in 9 files — first at assets/GrowthGuidePage-pv4tMz01.js:11666. Permissions LinkedIn Targeted Feed, Engage & Follow-Ups asks for tabs storage activeTab scripting alarms identity sidePanel \*://\*.linkedin.com/\* \*://\*.x.com/\* \*://\*.reddit.com/\* \*://\*.threads.com/\* \*://\*.facebook.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 LinkedIn Targeted Feed, Engage & Follow-Ups misuses it, and no match doesn't prove absence (minified or runtime-built code can hide it). We haven't traced where LinkedIn Targeted Feed, Engage & Follow-Ups sends data. [How we test](https://safe-outreach.com/how-we-test) ### How LinkedIn checks for LinkedIn Targeted Feed, Engage & Follow-Ups: 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://mnjjmehgakbgcgoeaahodkcdlidcjnjm/icons/icon16.png On LinkedIn’s AED list Yes 1 of 4,934 · snapshot Nov 2026 URL LinkedIn requests chrome-extension://mnjjmehgakbgcgoeaahodkcdlidcjnjm/icons/icon16.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 mnjjmehgakbg… or AedEvent; or Network → filter li/track to watch the verdict ship. The scan runs even in Incognito. Below — the full code-level teardown. ![LinkedIn Targeted Feed, Engage & Follow-Ups — marketed on the Chrome Web Store, detected by LinkedIn](https://storage.googleapis.com/linkedhelper-sot/checker/shots/mnjjmehgakbgcgoeaahodkcdlidcjnjm.webp) Vendor's own Chrome Web Store screenshot — this extension is on LinkedIn's detection list. ## How LinkedIn fingerprints your browser while you use LinkedIn Targeted Feed, Engage & Follow-Ups 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 LinkedIn Targeted Feed, Engage & Follow-Ups — each with its own code audit. - [Is Findymail safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-findymail-safe) - [Is Publer safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-publer-safe) - [Is Teamleader Integrations safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-teamleader-integrations-safe) - [Is Email Finder & Phone Enrichment safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-email-finder-phone-enrichment-safe) - [Is Tarss safe on LinkedIn? uploads session MEDIUM](https://safe-outreach.com/is-tarss-safe) - [Is ContactBook safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-contactbook-safe) [All extension checks](https://safe-outreach.com/deep-dives#all-checks) --- Source: https://safe-outreach.com/is-linkedin-targeted-feed-safe