--- title: "Is Klenty safe on LinkedIn in 2026?" description: "Does LinkedIn detect Klenty? It's on LinkedIn's active detection list. Checked against LinkedIn's own 4,934-extension list — see the verdict, the probe fi…" url: https://safe-outreach.com/is-klenty-email-outreach-tracking-from-gmail-safe date_published: 2026-11-07T08:00:11.679Z date_modified: 2026-11-07T00:00:00.000Z publisher: Safe Outreach --- # Is Klenty safe on LinkedIn in 2026? **No — LinkedIn detects Klenty** (we checked it November 7, 2026). Klenty's extension ID is on LinkedIn's AED detection list (Nov 2026 snapshot), and LinkedIn's page code checks for Klenty on every visit by requesting chrome-extension://dcobodbibhecmhnamioljhlnaeoimbcd/packages/tooltipster.bundle.min.js.LICENSE.txt — a file that exists only if Klenty is installed. Our automated scan of Klenty 1.12.67 found code that references LinkedIn's session cookie li\_at (7 matches in 3 files); whether Klenty sends that cookie anywhere needs a manual dataflow review. Updated November 7, 2026 · LinkedIn AED snapshot Nov 2026 ID: dcobodbibhecmhnamioljhlnaeoimbcd ## Does LinkedIn detect Klenty? 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://dcobodbibhecmhnamioljhlnaeoimbcd/packages/tooltipster.bundle.min.js.LICENSE.txt** 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 Klenty's code We downloaded Klenty version 1.12.67 from the Chrome Web Store on November 2, 2026 and searched its 20 code files for the patterns below. Each line shows the first place we found it. - Klenty's code references `li_at` — LinkedIn's session cookie, the one that keeps you logged in. 7 matches in 3 files — first at mailLoader.js:108. - Klenty's code references `JSESSIONID` — LinkedIn's CSRF cookie, needed to call LinkedIn's internal API as you. 7 matches in 3 files — first at mailLoader.js:108. - Klenty's code calls paths of LinkedIn's internal Voyager API (`voyager/api`). 2 matches in 2 files — first at serviceWorker.js:2. - Klenty uses the Chrome cookies API (`chrome.cookies`), which reads cookies of every site it has access to. 30 matches in 3 files — first at mailLoader.js:108. - Klenty reads or writes `document.cookie` inside pages. 2 matches in 1 file — first at mailLoader.js:108. - Klenty creates synthetic clicks or keystrokes (`dispatchEvent` / `MouseEvent`) — LinkedIn can tell these from real input (`isTrusted=false`). 96 matches in 5 files — first at mailLoader.js:2. - Klenty runs code built at runtime (`eval` / `new Function`). 10 matches in 5 files — first at mailLoader.js:108. - Klenty makes its own network requests (`fetch` / XHR / WebSocket). 80 matches in 6 files — first at mailLoader.js:2. - Klenty's code mentions linkedin.com. 70 matches in 5 files — first at mailLoader.js:108. Permissions Klenty asks for storage identity identity.email cookies tabs scripting webNavigation webRequest declarativeNetRequest management https://mail.google.com/\* https://\*.pipedrive.com/\* https://\*.salesforce.com/\* https://\*.lightning.force.com/\* https://www.linkedin.com/\* https://\*.klenty.com/\* https://\*.googleusercontent.com/proxy/\* https://cdnjs.cloudflare.com/\* https://accounts.google.com/ https://\*.zoho.eu/\* https://\*.zoho.in/\* https://\*.zoho.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 Klenty misuses it, and no match doesn't prove absence (minified or runtime-built code can hide it). We haven't traced where Klenty sends data. [How we test](https://safe-outreach.com/how-we-test) ### How LinkedIn checks for Klenty: 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://dcobodbibhecmhnamioljhlnaeoimbcd/packages/tooltipster.bundle.min.js.LICENSE.txt On LinkedIn’s AED list Yes 1 of 4,934 · snapshot Nov 2026 URL LinkedIn requests chrome-extension://dcobodbibhecmhnamioljhlnaeoimbcd/packages/tooltipster.bundle.min.js.LICENSE.txt 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 dcobodbibhec… or AedEvent; or Network → filter li/track to watch the verdict ship. The scan runs even in Incognito. Below — the full code-level teardown. ![Klenty — marketed on the Chrome Web Store, detected by LinkedIn](https://storage.googleapis.com/linkedhelper-sot/checker/shots/dcobodbibhecmhnamioljhlnaeoimbcd.webp) Vendor's own Chrome Web Store screenshot — this extension is on LinkedIn's detection list. ## How LinkedIn fingerprints your browser while you use Klenty 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 Klenty — each with its own code audit. - [Is OneClick safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-oneclick-job-tracker-safe) - [Is Lead411 Chrome Extension safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-lead411-chrome-extension-safe) - [Is Wiza safe on LinkedIn? uploads session HIGH](https://safe-outreach.com/is-wiza-safe) - [Is FlyMSG safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-flymsg-ai-writer-safe) - [Is Publer safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-publer-safe) - [Is Responsive CV safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-responsive-cv-resume-maker-from-linkedin-safe) [All extension checks](https://safe-outreach.com/deep-dives#all-checks) --- Source: https://safe-outreach.com/is-klenty-email-outreach-tracking-from-gmail-safe