this post was submitted on 01 Dec 2025
6 points (100.0% liked)
Privacy
4358 readers
44 users here now
Welcome! This is a community for all those who are interested in protecting their privacy.
Rules
PS: Don't be a smartass and try to game the system, we'll know if you're breaking the rules when we see it!
- Be civil and no prejudice
- Don't promote big-tech software
- No apathy and defeatism for privacy (i.e. "They already have my data, why bother?")
- No reposting of news that was already posted
- No crypto, blockchain, NFTs
- No Xitter links (if absolutely necessary, use xcancel)
Related communities:
Some of these are only vaguely related, but great communities.
- !opensource@programming.dev
- !selfhosting@slrpnk.net / !selfhosted@lemmy.world
- !piracy@lemmy.dbzer0.com
- !drm@lemmy.dbzer0.com
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments


The very first domain at the start of the spike is
pass-api.proton.me. I it could have been Proton Pass to leak the list of domains and apps I have an account for. Still I find that to be quite worrying, whether it was a bug or something else..Not used proton pass. Does it collect favicons by querying every host?
Could it possibly be some background check for valid domain names for proton pass? I imagine there could be a benefit to checking that the URLs associated with saved entries are actually live.
If the goal was exfiltrating a list of the sites you use, they don't really need to do it via some weird DNS stuff, since you're already expecting traffic directed at the proton api. They could just transfer an encrypted text file and call it a day. Doing this makes a ton of noise that you'd want to avoid if you were doing something shady, so it must serve some kind of function.
But why would they do that from an end user's device instead of their servers? And what about the unresolvable package names?
I'm leaning more towards a bug than exfiltration at this point, but it is still a somewhat serious leak. The contents of proton pass are end to end encrypted and thus supposed to be confidential, while this has caused my whole vault to be leaked to public DNS servers via unencrypted UDP. If it was intentional, it's terrible design. Maybe some intern thought to have the client grab favicons.
That's precisely why they can't do the scan from their servers. They don't know the domains - they're decrypted only on your device.
I feel like this is a tad dramatic. Surely, your vault contains more data, probably more sensitive, than just domain names.