--- title: "Is Hippo Video safe on LinkedIn in 2026?" description: "Does LinkedIn detect Hippo Video? It's on LinkedIn's active detection list. Checked against LinkedIn's own 4,934-extension list — see the verdict, the pro…" url: https://safe-outreach.com/is-hippo-video-video-and-screen-recorder-safe date_published: 2026-11-02T16:55:41.657Z date_modified: 2026-11-06T00:00:00.000Z publisher: Safe Outreach --- # Is Hippo Video safe on LinkedIn in 2026? **No — LinkedIn detects Hippo Video** (we checked it November 6, 2026). Hippo Video's extension ID is on LinkedIn's AED detection list (Nov 2026 snapshot), and LinkedIn's page code checks for Hippo Video on every visit by requesting chrome-extension://cijidiollmnkegoghpfobabpecdkeiah/assets/img/hippo/logo.png — a file that exists only if Hippo Video is installed. Our automated scan of Hippo Video 4.0.47 found code that references LinkedIn's session cookie li\_at (1 matches in 1 files); whether Hippo Video sends that cookie anywhere needs a manual dataflow review. Updated November 6, 2026 · LinkedIn AED snapshot Nov 2026 ID: cijidiollmnkegoghpfobabpecdkeiah ## Does LinkedIn detect Hippo Video? 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://cijidiollmnkegoghpfobabpecdkeiah/assets/img/hippo/logo.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 Hippo Video's code We downloaded Hippo Video version 4.0.47 from the Chrome Web Store on November 2, 2026 and searched its 95 code files for the patterns below. Each line shows the first place we found it. - Hippo Video'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:16. - Hippo Video'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.bundle.js:16. - Hippo Video's code calls paths of LinkedIn's internal Voyager API (`voyager/api`). 1 match in 1 file — first at background.bundle.js:16. - Hippo Video 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:16. - Hippo Video reads or writes `document.cookie` inside pages. 9 matches in 2 files — first at background.bundle.js:1. - Hippo Video creates synthetic clicks or keystrokes (`dispatchEvent` / `MouseEvent`) — LinkedIn can tell these from real input (`isTrusted=false`). 33 matches in 16 files — first at contentScript.bundle.js:108. - Hippo Video runs code built at runtime (`eval` / `new Function`). 3 matches in 1 file — first at recorder-sdk/hv\_recorder.js:533. - Hippo Video makes its own network requests (`fetch` / XHR / WebSocket). 149 matches in 48 files — first at background.bundle.js:1. - Hippo Video's code mentions linkedin.com. 19 matches in 4 files — first at background.bundle.js:16. Permissions Hippo Video asks for tabCapture tabs activeTab storage scripting identity management **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 Hippo Video misuses it, and no match doesn't prove absence (minified or runtime-built code can hide it). We haven't traced where Hippo Video sends data. [How we test](https://safe-outreach.com/how-we-test) ### How LinkedIn checks for Hippo Video: 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://cijidiollmnkegoghpfobabpecdkeiah/assets/img/hippo/logo.png On LinkedIn’s AED list Yes 1 of 4,934 · snapshot Nov 2026 URL LinkedIn requests chrome-extension://cijidiollmnkegoghpfobabpecdkeiah/assets/img/hippo/logo.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 cijidiollmnk… or AedEvent; or Network → filter li/track to watch the verdict ship. The scan runs even in Incognito. Below — the full code-level teardown. ![Hippo Video — marketed on the Chrome Web Store, detected by LinkedIn](https://storage.googleapis.com/linkedhelper-sot/checker/shots/cijidiollmnkegoghpfobabpecdkeiah.webp) Vendor's own Chrome Web Store screenshot — this extension is on LinkedIn's detection list. ## How LinkedIn fingerprints your browser while you use Hippo Video 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 Hippo Video — each with its own code audit. - [Is Post Formatter safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-post-formatter-linkedin-bold-text-more-styles-safe) - [Is AI Interviewer MIR by MirWork safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-ai-interviewer-mir-safe) - [Is Email Finder & Phone Enrichment safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-email-finder-phone-enrichment-safe) - [Is Datanyze Chrome Extension safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-datanyze-chrome-extension-safe) - [Is EasyGen safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-easygen-safe) - [Is LeadRocks for LinkedIn safe on LinkedIn? MEDIUM](https://safe-outreach.com/is-leadrocks-safe) [All extension checks](https://safe-outreach.com/deep-dives#all-checks) --- Source: https://safe-outreach.com/is-hippo-video-video-and-screen-recorder-safe