---
title: "Is OutreachGenie safe on LinkedIn in 2026?"
description: "Does LinkedIn detect OutreachGenie? It's on LinkedIn's active detection list. Checked against LinkedIn's own 4,934-extension list — see the verdict, the p…"
url: https://safe-outreach.com/is-outreachgenie-free-linkedin-outreach-automation-safe
date_published: 2026-11-19T08:01:48.228Z
date_modified: 2026-11-22T00:00:00.000Z
publisher: Safe Outreach
---

# Is OutreachGenie safe on LinkedIn in 2026?

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

Updated November 22, 2026 · LinkedIn AED snapshot Nov 2026

ID: obhopimnjblgeacanheabclcaehdmchg

## Does LinkedIn detect OutreachGenie? 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://obhopimnjblgeacanheabclcaehdmchg/sidebar.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 OutreachGenie's code

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

-   OutreachGenie's code references `li_at` — LinkedIn's session cookie, the one that keeps you logged in. 4 matches in 1 file — first at dist/background.js:56.
-   OutreachGenie's code references `JSESSIONID` — LinkedIn's CSRF cookie, needed to call LinkedIn's internal API as you. 5 matches in 3 files — first at dist/background.js:56.
-   OutreachGenie's code calls paths of LinkedIn's internal Voyager API (`voyager/api`). 61 matches in 6 files — first at dist/background.js:56.
-   OutreachGenie uses the Chrome cookies API (`chrome.cookies`), which reads cookies of every site it has access to. 1 match in 1 file — first at dist/background.js:69.
-   OutreachGenie reads or writes `document.cookie` inside pages. 2 matches in 1 file — first at dist/background.js:56.
-   OutreachGenie creates synthetic clicks or keystrokes (`dispatchEvent` / `MouseEvent`) — LinkedIn can tell these from real input (`isTrusted=false`). 51 matches in 4 files — first at dist/background.js:65.
-   OutreachGenie makes its own network requests (`fetch` / XHR / WebSocket). 59 matches in 6 files — first at dist/background.js:56.
-   OutreachGenie's code mentions linkedin.com. 374 matches in 8 files — first at dist/background.js:42.

Permissions OutreachGenie asks for

storage alarms cookies tabGroups scripting webRequest https://www.linkedin.com/\* https://static.licdn.com/\* https://realtime.www.linkedin.com/\* https://api.outreachgenie.ai/\* https://api.cloudinary.com/\* https://o4510719235784704.ingest.de.sentry.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 OutreachGenie misuses it, and no match doesn't prove absence (minified or runtime-built code can hide it). We haven't traced where OutreachGenie sends data. [How we test](https://safe-outreach.com/how-we-test)

### How LinkedIn checks for OutreachGenie: 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://obhopimnjblgeacanheabclcaehdmchg/sidebar.html

On LinkedIn’s AED list

Yes

1 of 4,934 · snapshot Nov 2026

URL LinkedIn requests

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

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

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

## How LinkedIn fingerprints your browser while you use OutreachGenie

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

-   [Is Wiza safe on LinkedIn? uploads session HIGH](https://safe-outreach.com/is-wiza-safe)
-   [Is Devi safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-devi-safe)
-   [Is SwipeWell safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-swipewell-safe)
-   [Is EasyGen safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-easygen-safe)
-   [Is ReSkinner safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-reskinner-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-outreachgenie-free-linkedin-outreach-automation-safe
