LinkedIn probes for 6,000+ Chrome extensions: what BrowserGate found and how it works

A LinkedIn script checks for 6,236 Chrome extensions and collects device data. How extension probing works, LinkedIn's response, and how to limit it.

TechLogHub Engineering Team
April 3, 2026
3 min read
0 views

Share Article

LinkedIn secretly scans for 6,000+ Chrome extensions and collects device data

In early April 2026 a report called "BrowserGate" accused LinkedIn of quietly scanning visitors' browsers for thousands of Chrome extensions and collecting device details. BleepingComputer confirmed that a LinkedIn script checks for 6,236 extensions. LinkedIn doesn't deny the detection but says it is used to fight scraping, not to profile people. For web developers and extension authors, the interesting part is how easily any website can do this, and what extensions can do to make themselves harder to detect.

What happened

The BrowserGate report was published by Fairlinked e.V., an association that says it represents commercial LinkedIn users. LinkedIn says the report's author is linked to a company whose LinkedIn account was restricted for scraping. The report claims LinkedIn ties extension data to identified members and uses it to spot users of more than 200 competing sales tools such as Apollo, Lusha and ZoomInfo. It also claims LinkedIn has sent enforcement threats based on the results.

BleepingComputer examined the page and found a script, loaded from a randomised filename, that checks for 6,236 extensions. A 2025 version checked about 2,000, and a GitHub repository from early 2026 listed about 3,000. The script also collects CPU core count, available memory, screen resolution, time zone, language, battery status, audio information and storage features. BleepingComputer could confirm the scanning but not how the data is used or whether it is shared.

LinkedIn called the claims "plain wrong". It says detection helps it find extensions that scrape member data without consent and protects site stability, and that it does not use the data "to infer sensitive information about members". A German court had earlier refused a preliminary injunction sought by Teamfluence, the developer of a LinkedIn tool, finding LinkedIn's measures were not unlawful obstruction. In September 2026 a US federal judge in the Northern District of California dismissed two proposed class actions over the scanning for lack of standing.

Who is affected

  • Chrome and Chromium browser users who visit LinkedIn, especially those running sales, automation or scraping extensions.
  • Extension developers whose extensions expose web-accessible resources that make them detectable.
  • Companies building browser fingerprinting into their own sites, who face the same legal and trust questions.

What it means for developers and engineering teams

Extension probing is an old technique. Chrome extensions can declare web_accessible_resources, files that web pages are allowed to load from chrome-extension://<extension-id>/<path>. Extension IDs are fixed and public, so a page can try to load a known file for each extension it cares about. If the request succeeds the extension is installed, and if it fails it isn't. LinkedIn describes its check as testing whether "a static resource URL exists". Repeat that a few thousand times and you get a detailed fingerprint, and on a site where users are signed in, it can be tied to a real identity.

Firefox is less exposed because it gives each installed extension a random per-install UUID in its moz-extension:// URLs. In Chrome, the main defence is in the extension author's hands.

For teams building sites, device and extension fingerprinting is legally sensitive. In the EU, reading information from a user's device generally needs consent unless it is strictly necessary, and "anti-scraping" is the kind of justification regulators examine closely. Be prepared to explain it in your privacy notice.

What to do now

  1. Extension developers: minimise web_accessible_resources. Expose only the files you need and restrict them with matches to the sites that need them:
    "web_accessible_resources": [{
      "resources": ["inject.js"],
      "matches": ["https://app.example.com/*"]
    }]
  2. Audit your own manifests for broad patterns like "resources": ["*"] with "matches": ["<all_urls>"], which make your extension detectable from every site.
  3. Users and IT teams: keep work and personal browsing in separate profiles, and remove extensions you don't actively use. Fewer extensions means a less unique fingerprint.
  4. Site owners: if you fingerprint for fraud or abuse prevention, document it, minimise what you collect, set retention limits, and check whether you need consent under GDPR and ePrivacy rules.
  5. Check what your own pages run. Third-party scripts can fingerprint too. A Content Security Policy and a script inventory show what is loaded.

Related on TechLogHub

  • SAM: an open-source blocker with fingerprint protection
  • DOM: what page scripts can read

Sources

Stay Updated

Get the next deep dive in your inbox

Subscribe for product analysis, engineering explainers, and practical guides published on TechLogHub.

See what launched this week

One email a week: new and trending developer tools, fresh comparisons, and what shipped. Unsubscribe in one click.

LinkedIn Chrome Extension Scanning: BrowserGate Explained | Linkedin Secretly Scans For 6000 Plus Chrome Extensions