33
BrowserGate: Technical breakdown of LinkedIn’s covert browser extension fingerprinting
(the.unknown-universe.co.uk)
this post was submitted on 03 Apr 2026
33 points (100.0% liked)
Privacy
9464 readers
1039 users here now
A community for Lemmy users interested in privacy
Rules:
- Be civil
- No spam posting
- Keep posts on-topic
- No trolling
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
First off it only scans browser addons/extensions by matching them to known browser ids.
Second this has nothing to do with home lab or network so nothing to secure there; Either dont use linkedin, use a firefox based browser or, if you read the actual browsergate website, changing your user agent to anything not chrome/chromium based should block the script from running as it runs this check before anything else, or just dns block 'linkedin.com/li/track' iirc to prevent from being sent back or do all of the above.
Yes this is a volation of privacy but helping push the framing around this thst it scans your computer with that terrible title isnt helping the situation.
Edit: spelling
Thanks for the feedback. You’re right, it’s really just scanning for known extension IDs, not poking around your entire computer. Saying “computer scan” might sound a bit dramatic, but the privacy risk is still pretty serious given what info they can guess from those extensions.
About the home lab and network side — I get that LinkedIn isn’t scanning your whole network or anything. What I meant is more about how you can block or filter those sneaky requests at the network level, like with DNS blocking or firewall rules, so they never even get sent out. It’s not a classic home lab threat, but if you’re running your own DNS or network filters, it’s a handy extra layer to keep things tighter.
Sure, switching browsers or faking your user agent works too, but not everyone wants to give up Chromium or LinkedIn completely. That’s why I mentioned a few different ways to protect yourself.
Appreciate the note on wording — I just wanted to show why this isn’t just some minor browser oddity and why it’s worth thinking about from a privacy and network defence angle.
How do you DNS block a URL :)