---
title: "Is SalesPrompter for LinkedIn safe on LinkedIn in 2026?"
description: "Does LinkedIn detect SalesPrompter for LinkedIn? It's on LinkedIn's active detection list. Checked against LinkedIn's own 4,934-extension list — see the v…"
url: https://safe-outreach.com/is-salesprompter-safe
date_published: 2026-11-20T08:05:59.203Z
date_modified: 2026-11-22T00:00:00.000Z
publisher: Safe Outreach
---

# Is SalesPrompter for LinkedIn safe on LinkedIn in 2026?

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

Updated November 22, 2026 · LinkedIn AED snapshot Nov 2026

ID: pfmbhdbhllglinbdgfckkajcfcabeknl

## Does LinkedIn detect SalesPrompter for LinkedIn? 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://pfmbhdbhllglinbdgfckkajcfcabeknl/icon-128.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 SalesPrompter for LinkedIn's code

We downloaded SalesPrompter for LinkedIn version 0.1.10 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.

-   SalesPrompter for LinkedIn's code references `li_at` — LinkedIn's session cookie, the one that keeps you logged in. 1 match in 1 file — first at background.bundle.js:1.
-   SalesPrompter for LinkedIn's code calls paths of LinkedIn's internal Voyager API (`voyager/api`). 1 match in 1 file — first at contentScript.bundle.js:1.
-   SalesPrompter for LinkedIn uses the Chrome cookies API (`chrome.cookies`), which reads cookies of every site it has access to. 1 match in 1 file — first at background.bundle.js:1.
-   SalesPrompter for LinkedIn creates synthetic clicks or keystrokes (`dispatchEvent` / `MouseEvent`) — LinkedIn can tell these from real input (`isTrusted=false`). 7 matches in 2 files — first at contentScript.bundle.js:1.
-   SalesPrompter for LinkedIn makes its own network requests (`fetch` / XHR / WebSocket). 5 matches in 1 file — first at contentScript.bundle.js:1.
-   SalesPrompter for LinkedIn's code mentions linkedin.com. 4 matches in 3 files — first at background.bundle.js:1.

Permissions SalesPrompter for LinkedIn asks for

storage cookies identity identity.email declarativeNetRequest https://www.linkedin.com/\* https://linkedgpt-main-aad6f04.zuplo.app/\* https://eofvwgntqlwrqb.m.pipedream.net/\* https://eowl6d9c2gcy8ll.m.pipedream.net/\* https://eo59de5jude0ydc.m.pipedream.net/\*

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

### How LinkedIn checks for SalesPrompter for LinkedIn: 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://pfmbhdbhllglinbdgfckkajcfcabeknl/icon-128.png

On LinkedIn’s AED list

Yes

1 of 4,934 · snapshot Nov 2026

URL LinkedIn requests

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

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

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

## How LinkedIn fingerprints your browser while you use SalesPrompter for LinkedIn

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 SalesPrompter for LinkedIn — each with its own code audit.

-   [Is ZoomInfo safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-zoominfo-safe)
-   [Is GetProspect v7.0.5 safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-getprospect-safe)
-   [Is ConnectGenie safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-connectgenie-safe)
-   [Is Linked Apply Bot safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-linked-apply-bot-safe)
-   [Is Apollo safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-apollo-safe)
-   [Is Distraction Free for LinkedIn™ safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-distraction-free-safe)

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

---
Source: https://safe-outreach.com/is-salesprompter-safe
