--- title: "Is Email finder by soujiyi.com safe on LinkedIn in 2026?" description: "Does LinkedIn detect Email finder by soujiyi.com? It's on LinkedIn's active detection list. Checked against LinkedIn's own 4,934-extension list — see the …" url: https://safe-outreach.com/is-email-finder-safe date_published: 2026-11-04T08:02:21.667Z date_modified: 2026-11-06T00:00:00.000Z publisher: Safe Outreach --- # Is Email finder by soujiyi.com safe on LinkedIn in 2026? **No — LinkedIn detects Email finder by soujiyi.com** (we checked it November 6, 2026). Email finder by soujiyi.com's extension ID is on LinkedIn's AED detection list (Nov 2026 snapshot), and LinkedIn's page code checks for Email finder by soujiyi.com on every visit by requesting chrome-extension://chbphidecmndldfgbknkbkekbhojicem/query-id.js — a file that exists only if Email finder by soujiyi.com is installed. Our automated scan of Email finder by soujiyi.com 4.0.1 found code that references LinkedIn's session cookie li\_at (2 matches in 2 files); whether Email finder by soujiyi.com sends that cookie anywhere needs a manual dataflow review. Updated November 6, 2026 · LinkedIn AED snapshot Nov 2026 ID: chbphidecmndldfgbknkbkekbhojicem ## Does LinkedIn detect Email finder by soujiyi.com? 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://chbphidecmndldfgbknkbkekbhojicem/query-id.js** 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 Email finder by soujiyi.com's code We downloaded Email finder by soujiyi.com version 4.0.1 from the Chrome Web Store on November 2, 2026 and searched its 28 code files for the patterns below. Each line shows the first place we found it. - Email finder by soujiyi.com's code references `li_at` — LinkedIn's session cookie, the one that keeps you logged in. 2 matches in 2 files — first at content-new.js:1. - Email finder by soujiyi.com's code references `JSESSIONID` — LinkedIn's CSRF cookie, needed to call LinkedIn's internal API as you. 1 match in 1 file — first at background-new.js:1. - Email finder by soujiyi.com's code calls paths of LinkedIn's internal Voyager API (`voyager/api`). 5 matches in 1 file — first at background-new.js:1. - Email finder by soujiyi.com uses the Chrome cookies API (`chrome.cookies`), which reads cookies of every site it has access to. 4 matches in 1 file — first at background-new.js:1. - Email finder by soujiyi.com runs code built at runtime (`eval` / `new Function`). 1 match in 1 file — first at utils/infiniteScroll.js:1. - Email finder by soujiyi.com makes its own network requests (`fetch` / XHR / WebSocket). 27 matches in 9 files — first at common.js:1. - Email finder by soujiyi.com's code mentions linkedin.com. 41 matches in 8 files — first at background.js:1. Permissions Email finder by soujiyi.com asks for storage tabs activeTab scripting contextMenus unlimitedStorage cookies http://\*/\* 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 Email finder by soujiyi.com misuses it, and no match doesn't prove absence (minified or runtime-built code can hide it). We haven't traced where Email finder by soujiyi.com sends data. [How we test](https://safe-outreach.com/how-we-test) ### How LinkedIn checks for Email finder by soujiyi.com: 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://chbphidecmndldfgbknkbkekbhojicem/query-id.js On LinkedIn’s AED list Yes 1 of 4,934 · snapshot Nov 2026 URL LinkedIn requests chrome-extension://chbphidecmndldfgbknkbkekbhojicem/query-id.js 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 chbphidecmnd… or AedEvent; or Network → filter li/track to watch the verdict ship. The scan runs even in Incognito. Below — the full code-level teardown. ![Email finder by soujiyi.com — marketed on the Chrome Web Store, detected by LinkedIn](https://storage.googleapis.com/linkedhelper-sot/checker/shots/chbphidecmndldfgbknkbkekbhojicem.webp) Vendor's own Chrome Web Store screenshot — this extension is on LinkedIn's detection list. ## How LinkedIn fingerprints your browser while you use Email finder by soujiyi.com 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 Email finder by soujiyi.com — each with its own code audit. - [Is Axonaut safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-axonaut-safe) - [Is Coral Starfish for Invenias safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-coral-starfish-safe) - [Is LinkedIn Text Formatter safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-linkedin-text-formatter-ablc-safe) - [Is AI Text Expander safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-ai-text-expander-snippets-and-templates-safe) - [Is Lemlist safe on LinkedIn? uploads session HIGH](https://safe-outreach.com/is-lemlist-safe) - [Is CommenTron safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-commentron-safe) [All extension checks](https://safe-outreach.com/deep-dives#all-checks) --- Source: https://safe-outreach.com/is-email-finder-safe