---
title: "Is Crew CRM safe on LinkedIn in 2026?"
description: "Does LinkedIn detect Crew CRM? It's on LinkedIn's active detection list. Checked against LinkedIn's own 4,934-extension list — see the verdict, the probe …"
url: https://safe-outreach.com/is-crew-crm-safe
date_published: 2026-11-22T19:45:12.018Z
date_modified: 2026-11-22T19:45:12.018Z
publisher: Safe Outreach
---

# Is Crew CRM safe on LinkedIn in 2026?

**No — LinkedIn detects Crew CRM** (we checked it November 22, 2026). Crew CRM's extension ID is on LinkedIn's AED detection list (Nov 2026 snapshot), and LinkedIn's page code checks for Crew CRM on every visit by requesting chrome-extension://dimfhhnadapnnbcgkdmbcdafndjblcfa/scripts/credentials.js — a file that exists only if Crew CRM is installed. Our automated scan of Crew CRM 1.18.33 found code that references LinkedIn's session cookie li\_at (1 matches in 1 files); whether Crew CRM sends that cookie anywhere needs a manual dataflow review.

Updated November 22, 2026 · LinkedIn AED snapshot Nov 2026

ID: dimfhhnadapnnbcgkdmbcdafndjblcfa

## Does LinkedIn detect Crew CRM? 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://dimfhhnadapnnbcgkdmbcdafndjblcfa/scripts/credentials.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 Crew CRM's code

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

-   Crew CRM's code references `li_at` — LinkedIn's session cookie, the one that keeps you logged in. 1 match in 1 file — first at scripts/background.js:1.
-   Crew CRM's code references `JSESSIONID` — LinkedIn's CSRF cookie, needed to call LinkedIn's internal API as you. 2 matches in 1 file — first at content/index.js:134.
-   Crew CRM's code calls paths of LinkedIn's internal Voyager API (`voyager/api`). 1 match in 1 file — first at content/index.js:1123.
-   Crew CRM uses the Chrome cookies API (`chrome.cookies`), which reads cookies of every site it has access to. 7 matches in 2 files — first at scripts/background.js:1.
-   Crew CRM reads or writes `document.cookie` inside pages. 9 matches in 1 file — first at content/index.js:25.
-   Crew CRM creates synthetic clicks or keystrokes (`dispatchEvent` / `MouseEvent`) — LinkedIn can tell these from real input (`isTrusted=false`). 34 matches in 1 file — first at content/index.js:17.
-   Crew CRM makes its own network requests (`fetch` / XHR / WebSocket). 27 matches in 1 file — first at content/index.js:17.
-   Crew CRM's code mentions linkedin.com. 74 matches in 4 files — first at content/index.js:126.

Permissions Crew CRM asks for

activeTab tabs scripting contextMenus management cookies storage \*://\*.linkedin.com/\* \*://app.crewcrm.work/\* \*://app.build.crewcrm.work/\*

**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 Crew CRM misuses it, and no match doesn't prove absence (minified or runtime-built code can hide it). We haven't traced where Crew CRM sends data. [How we test](https://safe-outreach.com/how-we-test)

### How LinkedIn checks for Crew CRM: 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://dimfhhnadapnnbcgkdmbcdafndjblcfa/scripts/credentials.js

On LinkedIn’s AED list

Yes

1 of 4,934 · snapshot Nov 2026

URL LinkedIn requests

chrome-extension://dimfhhnadapnnbcgkdmbcdafndjblcfa/scripts/credentials.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 dimfhhnadapn… or AedEvent; or Network → filter li/track to watch the verdict ship. The scan runs even in Incognito. Below — the full code-level teardown.

![Crew CRM — marketed on the Chrome Web Store, detected by LinkedIn](https://storage.googleapis.com/linkedhelper-sot/checker/shots/dimfhhnadapnnbcgkdmbcdafndjblcfa.webp)

Vendor's own Chrome Web Store screenshot — this extension is on LinkedIn's detection list.

## How LinkedIn fingerprints your browser while you use Crew CRM

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 Crew CRM — each with its own code audit.

-   [Is Salee safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-salee-safe)
-   [Is Replai safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-replai-safe)
-   [Is FindThatLead safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-findthatlead-safe)
-   [Is Copper CRM for Gmail and LinkedIn safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-copper-crm-safe)
-   [Is CRM, Phone Number & Email Finder for LinkedIn safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-crm-safe)
-   [Is GetProspect v7.0.5 safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-getprospect-safe)

[All extension checks](https://safe-outreach.com/deep-dives#all-checks)

---
Source: https://safe-outreach.com/is-crew-crm-safe
