LinkedIn Fingerprints 6,000+ Chrome Extensions, Builds Device Profiles on Users
Original source
LinkedIn secretely scans for 6,000+ Chrome extensions, collects data
BleepingComputer →LinkedIn injects a randomized-filename JavaScript file into user sessions that probes for over 6,236 Chrome extensions by attempting to fetch static resources tied to each extension ID — a standard side-channel detection technique. The script also harvests CPU core count, RAM, screen resolution, timezone, battery status, and audio/storage metadata. The scope has grown rapidly: roughly 2,000 extensions were targeted in early 2025, 3,000 two months ago, and 6,236 now. The scanned set includes not just scraping and sales-intelligence tools but also grammar checkers and tax software with no obvious connection to platform abuse.
LinkedIn acknowledges the scanning but frames it narrowly as a ToS enforcement mechanism — detecting extensions that scrape member data without consent or destabilize the platform by generating abnormal request volumes. The company also attributes the BrowserGate report to the developer of a LinkedIn extension called Teamfluence, whose account was restricted for scraping. A German court denied that developer’s injunction request and found their own data practices legally problematic, which LinkedIn cites as evidence the report is a retaliatory PR campaign.
The undisputed core remains: a major platform is systematically fingerprinting visitors’ browser environments and linking results to authenticated, real-identity profiles tied to employers and job roles. Whether the collected data is used for anything beyond abuse detection is unverified, but the technique is identical to methods historically used for cross-site tracking. The eBay precedent from 2021 — port-scanning visitors ostensibly for fraud prevention — shows how ‘security justification’ can mask broad surveillance infrastructure that later spreads across industries.
Read the full article
Continue reading at BleepingComputer →This is an AI-generated summary. Read the original for the full story.