--- title: "Is Nicoka Extension safe on LinkedIn in 2026?" description: "Does LinkedIn detect Nicoka Extension? It's on LinkedIn's active detection list. Checked against LinkedIn's own 4,934-extension list — see the verdict, th…" url: https://safe-outreach.com/is-nicoka-extension-safe date_published: 2026-11-09T08:01:31.057Z date_modified: 2026-11-11T00:00:00.000Z publisher: Safe Outreach --- # Is Nicoka Extension safe on LinkedIn in 2026? **No — LinkedIn detects Nicoka Extension** (we checked it November 11, 2026). Nicoka Extension's extension ID is on LinkedIn's AED detection list (Nov 2026 snapshot), and LinkedIn's page code checks for Nicoka Extension on every visit by requesting chrome-extension://malloejfbmjgjahabjakgicekcgejhkg/index.html — a file that exists only if Nicoka Extension is installed. Our automated scan of Nicoka Extension 3.6.7 found code that references LinkedIn's session cookie li\_at (3 matches in 1 files); whether Nicoka Extension sends that cookie anywhere needs a manual dataflow review. Updated November 11, 2026 · LinkedIn AED snapshot Nov 2026 ID: malloejfbmjgjahabjakgicekcgejhkg ## Does LinkedIn detect Nicoka Extension? 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://malloejfbmjgjahabjakgicekcgejhkg/index.html** 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 Nicoka Extension's code We downloaded Nicoka Extension version 3.6.7 from the Chrome Web Store on November 2, 2026 and searched its 22 code files for the patterns below. Each line shows the first place we found it. - Nicoka Extension'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-B\_kjUFnn.js:35. - Nicoka Extension's code references `JSESSIONID` — LinkedIn's CSRF cookie, needed to call LinkedIn's internal API as you. 5 matches in 1 file — first at assets/index-B\_kjUFnn.js:18. - Nicoka Extension's code calls paths of LinkedIn's internal Voyager API (`voyager/api`). 3 matches in 1 file — first at assets/index-B\_kjUFnn.js:12. - Nicoka Extension uses the Chrome cookies API (`chrome.cookies`), which reads cookies of every site it has access to. 12 matches in 1 file — first at assets/index-B\_kjUFnn.js:18. - Nicoka Extension reads or writes `document.cookie` inside pages. 2 matches in 1 file — first at assets/vendor-DMsvLz4J.js:193. - Nicoka Extension creates synthetic clicks or keystrokes (`dispatchEvent` / `MouseEvent`) — LinkedIn can tell these from real input (`isTrusted=false`). 58 matches in 4 files — first at utils/france-travail.js:299. - Nicoka Extension runs code built at runtime (`eval` / `new Function`). 1 match in 1 file — first at assets/vendor-DMsvLz4J.js:204. - Nicoka Extension makes its own network requests (`fetch` / XHR / WebSocket). 30 matches in 10 files — first at messages.js:597. - Nicoka Extension's code mentions linkedin.com. 36 matches in 3 files — first at messages.js:788. Permissions Nicoka Extension asks for activeTab webNavigation cookies sidePanel clipboardWrite downloads https://\*.linkedin.com/\* https://\*.apec.fr/\* https://\*.hellowork.com/\* https://\*.cvaden.com/\* https://\*.francetravail.fr/\* https://\*.turnover-it.com/\* https://\*.indeed.com/\* https://\*.meteojob.com/\* https://\*.agefiph.fr/\* https://\*.pappers.fr/\* https://\*.app.muzzo.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 Nicoka Extension misuses it, and no match doesn't prove absence (minified or runtime-built code can hide it). We haven't traced where Nicoka Extension sends data. [How we test](https://safe-outreach.com/how-we-test) ### How LinkedIn checks for Nicoka Extension: 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://malloejfbmjgjahabjakgicekcgejhkg/index.html On LinkedIn’s AED list Yes 1 of 4,934 · snapshot Nov 2026 URL LinkedIn requests chrome-extension://malloejfbmjgjahabjakgicekcgejhkg/index.html 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 malloejfbmjg… or AedEvent; or Network → filter li/track to watch the verdict ship. The scan runs even in Incognito. Below — the full code-level teardown. ![Nicoka Extension — marketed on the Chrome Web Store, detected by LinkedIn](https://storage.googleapis.com/linkedhelper-sot/checker/shots/malloejfbmjgjahabjakgicekcgejhkg.webp) Vendor's own Chrome Web Store screenshot — this extension is on LinkedIn's detection list. ## How LinkedIn fingerprints your browser while you use Nicoka Extension 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 Nicoka Extension — each with its own code audit. - [Is Leadfeeder Connect safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-leadfeeder-connect-safe) - [Is LinkOff safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-linkoff-safe) - [Is Linked Apply Bot safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-linked-apply-bot-safe) - [Is SwipeWell safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-swipewell-safe) - [Is PhantomBuster safe on LinkedIn? HIGH](https://safe-outreach.com/is-phantombuster-safe) - [Is WhenX safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-whenx-mark-linkedin-profiles-with-notes-safe) [All extension checks](https://safe-outreach.com/deep-dives#all-checks) --- Source: https://safe-outreach.com/is-nicoka-extension-safe