Is Lighthouse Insights safe on LinkedIn in 2026?
No — LinkedIn detects Lighthouse Insights (we checked it ). Lighthouse Insights's extension ID is on LinkedIn's AED detection list (Nov 2026 snapshot), and LinkedIn's page code checks for Lighthouse Insights on every visit by requesting chrome-extension://enolpocjfhedjgoeggfakiphoghlhnnm/index.html — a file that exists only if Lighthouse Insights is installed. Our automated scan of Lighthouse Insights 2.3.24 found code that references LinkedIn's session cookie li_at (1 matches in 1 files); whether Lighthouse Insights sends that cookie anywhere needs a manual dataflow review.
Updated · LinkedIn AED snapshot Nov 2026
Does LinkedIn detect Lighthouse Insights? What we found in its code
This browser extension is actively compiled into LinkedIn's frontend detection lists. LinkedIn's scripts can detect when this is active on your browser.
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).
What our automated scan found in Lighthouse Insights's code
We downloaded Lighthouse Insights version 2.3.24 from the Chrome Web Store on and searched its 50 code files for the patterns below. Each line shows the first place we found it.
- Lighthouse Insights's code references
li_at— LinkedIn's session cookie, the one that keeps you logged in. 1 match in 1 file — first at background.js:1. - Lighthouse Insights's code references
JSESSIONID— LinkedIn's CSRF cookie, needed to call LinkedIn's internal API as you. 1 match in 1 file — first at assets/ExtensionSettings-BAGlWL6o.js:1. - Lighthouse Insights's code calls paths of LinkedIn's internal Voyager API (
voyager/api). 1 match in 1 file — first at assets/ExtensionSettings-BAGlWL6o.js:1. - Lighthouse Insights uses the Chrome cookies API (
chrome.cookies), which reads cookies of every site it has access to. 2 matches in 1 file — first at background.js:1. - Lighthouse Insights reads or writes
document.cookieinside pages. 5 matches in 3 files — first at assets/AuthenticatedExtension-423xzWDJ.js:2. - Lighthouse Insights creates synthetic clicks or keystrokes (
dispatchEvent/MouseEvent) — LinkedIn can tell these from real input (isTrusted=false). 54 matches in 11 files — first at assets/AuthenticatedExtension-423xzWDJ.js:2. - Lighthouse Insights runs code built at runtime (
eval/new Function). 3 matches in 2 files — first at assets/AuthenticatedExtension-423xzWDJ.js:2. - Lighthouse Insights makes its own network requests (
fetch/ XHR / WebSocket). 42 matches in 8 files — first at assets/AuthenticatedExtension-423xzWDJ.js:2. - Lighthouse Insights's code mentions linkedin.com. 40 matches in 11 files — first at background.js:1.
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 Lighthouse Insights misuses it, and no match doesn't prove absence (minified or runtime-built code can hide it). We haven't traced where Lighthouse Insights sends data. How we test
How LinkedIn checks for Lighthouse Insights: 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 reverse-engineered line by line:
// chrome-extension://enolpocjfhedjgoeggfakiphoghlhnnm/index.html

How LinkedIn fingerprints your browser while you use Lighthouse Insights
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.
Canvas render hash: Draws a hidden shape and hashes the pixels — GPU/driver quirks make it near-unique. (illustrative — e.g. a1f9…3e0c)
WebGL parameters: 65+ GPU/renderer values read straight from the graphics driver. (illustrative — e.g. ANGLE (Apple, M2 Pro))
AudioContext: Plays an inaudible tone and hashes tiny hardware-specific waveform differences. (illustrative — e.g. 124.0432…)
Installed fonts: Measures text rendering to infer which fonts are installed on your machine. (illustrative — e.g. 38 fonts)
Local IP (WebRTC): A WebRTC leak reveals your real local network IP, even behind a VPN. (illustrative — e.g. 192.168.1.x)
Timezone ×2: Checked two different ways — a mismatch between them is itself a signal. (illustrative — e.g. Europe/Warsaw)
Hardware & OS: CPU core count, device memory, screen size/depth, platform string. (illustrative — e.g. 8 cores · macOS)
navigator.webdriver: Chrome's own automation flag — true when a page is driven by Selenium/Puppeteer. (illustrative — e.g. false)
Cameras & mics: Enumerates connected media devices without asking permission to use them. (illustrative — e.g. 1 camera · 2 mics)
Incognito flag: A filesystem-quota heuristic that detects private-browsing mode. (illustrative — e.g. false)
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.
Similar LinkedIn tools we checked
Same architecture and risk as Lighthouse Insights — each with its own code audit.
- Is LigoAI safe on LinkedIn?MEDIUM
- Is Jobalytics safe on LinkedIn?MEDIUM
- Is Datanyze Chrome Extension safe on LinkedIn?MEDIUM
- Is Kanbox, Linkedin Automation and CRM safe on LinkedIn?uploads sessionHIGH
- Is Surfe safe on LinkedIn?uploads sessionHIGH
- Is LeadRocks for LinkedIn safe on LinkedIn?MEDIUM