We are discontinuing the dark web report
Posted by satertek 1 day ago
Comments
Comment by prepend 20 hours ago
I have a common name Gmail account. The password is rather complex and I would be surprised if it leaks as only I and Google know it. However, I would get reports that it’s on the dark web with blanked out password values. So I never knew if they actually compromised or just something else.
They would also report when some random site that used my Gmail address as user id was on the darknet that I don’t care about. I don’t care if my fidofido account is leaked. I never use it and if I did, then I would reset.
I think if the data were useful Google would have kept this up.
I bet they keep tracking though, just keep the reports internal.
Comment by nomilk 8 hours ago
Tangental, but I found 'Have I Been Pwned' useless too because you can't enter your email and find leaked passwords associated with the address, instead you have to enter each password (and repeat for every password you want to check).
I know there's an explanation that the raw password is not being sent and instead being hashed locally and only part of the hash is sent. But I don't know how to verify that and it feels wild to type passwords into a random website. (if anyone knows how to verify HIBP does only what it says it does [rather than blindly trust and hope for the best], would love to read more about it)
Comment by clarionbell 7 hours ago
Almost everyone interested in checking for password leaks knows how to generate SHA256 of a string. And those who don't shouldn't put their passwords on the internet.
Or even better, generate hash for all passwords in the database, package these hashes together with a simple search script and let people download it. That way, you are not sending any information anywhere, and noone can exploit the passwords, because hash is a one way function.
Then again, that download could be really large. I admit I have no idea how much storage would that take. But it's just text, so easily compressible. And with some smart indexing, it should be possible to keep most compressed and only unpack a relatively small portion to find a complete match.
Then again, I have virtually no background in cryptography, could be something horribly wrong with this.
Comment by eXpl0it3r 5 hours ago
When you do a check on https://haveibeenpwned.com/Passwords nothing is sent to the server. Instead the password is hashed locally and a list of the hash range is downloaded, which contains all the hashes and the number of occurrences.
The server doesn't receive the password, neither in plain-text nor hash form.
Comment by account42 2 hours ago
Comment by godelski 3 hours ago
Comment by sharperguy 2 hours ago
* user submits password * gets hashed client side * server compares it against stored hashes * server also re-hashes the stored hash, and compares it against the hash received from the client
This would effectively mean that either entering the password, or the password hash would correctly match, since when entering the hash you are effectively "double" hashing the password which gets compared to the double hashed password on the server.
The upside is that users who don't understand hashing or don't feel like opening a sha256 tool wouldn't have to change their behavior or even be confused by a dialog explaining why they should hash the input, while advanced users could find out about the feature via another channel (e.g. hackernews).
The downside would be that it adds an extra hash step to every comparison on the sever. It's hard to know how expensive this would be for them.
Comment by culi 7 hours ago
Though perhaps there could be a service where you enter in an email address and it sends an email to that address containing the passwords. That would be a slightly more complicated server to set up though
Comment by IAmBroom 6 minutes ago
It doesn't use any information that's not already exposed.
It reveals the extent of my problem to me.
Comment by thesuitonym 17 hours ago
The worst part is, it was an email address I hadn't used in about 10 years, and they wouldn't let me take it out of the report.
Comment by deepsun 15 hours ago
Comment by thesuitonym 24 minutes ago
Comment by placatedmayhem 13 hours ago
Comment by deepsun 12 hours ago
There are tens of services where I'd like it disposable, but hundreds of services where account is warranted. And some of those thousands will be compromised some day.
Comment by godelski 3 hours ago
Comment by Terr_ 8 hours ago
I have my own domain, and pay a hosting company to manage the e-mail, which means it's easy to have ton of forwarding-only addresses for different purposes.
This means that I register with mybank123@domain, if that ever leaks I can log in with them and change my e-mail to a new forwarding-address of mybank456@domain. Then retire the older one.
Comment by liquidgecka 9 hours ago
Comment by thaumasiotes 9 hours ago
What are the common two-letter first or last names?
Comment by tczMUFlmoNk 8 hours ago
For first names… Jo, Ty, Al, maybe?
Comment by bobthepanda 8 hours ago
Comment by password-app 11 hours ago
Alternatives: haveibeenpwned.com (free), 1Password Watchtower, Bitwarden breach reports.
The harder part isn't knowing about breaches—it's actually rotating passwords afterward. Most people know they should but don't because it's tedious.
Automated rotation tools are emerging but need careful security architecture (local-only, zero-knowledge) to avoid creating new attack vectors.
Comment by MinimalAction 17 hours ago
Comment by therein 16 hours ago
Comment by levocardia 16 hours ago
Comment by permo-w 10 hours ago
Comment by mholt 14 hours ago
Comment by rolph 16 hours ago
Comment by atomic128 18 hours ago
Comment by strathmeyer 13 hours ago
Comment by xxmarkuski 19 hours ago
Comment by bflesch 17 hours ago
Comment by Mistletoe 12 hours ago
Comment by eimrine 1 day ago
Comment by stuaxo 22 hours ago
Comment by arccy 19 hours ago
Comment by breppp 18 hours ago
I remember email and phone being the major ones. A kind of improved haveibeenpwned
Comment by lavezzi 17 hours ago
Comment by tonytamps 18 hours ago
Comment by pluto_modadic 23 hours ago
Comment by martythemaniak 17 hours ago
Comment by rolph 16 hours ago
such a product must be crafted to mitigate its own abuse, as well as the original problem.
Comment by 9dev 1 day ago
Comment by moebrowne 1 day ago
Comment by sunaookami 23 hours ago
Comment by extraduder_ire 15 hours ago
I know it's still active because I see someone with that handle posting on bluesky regularly.
Comment by 7bit 23 hours ago
Translation: We don’t actually want to keep spending time, money, and resources on this.
Comment by eitally 13 hours ago
This is one where I don't blame them for killing it because "it" wasn't really even a product -- it was just a very basic, not useful at all, report.
Comment by nospice 17 hours ago
Comment by jajuuka 23 hours ago
Comment by ikiris 16 hours ago