Comment by eterm
3 months ago
> Chrome told me my PureGym PIN had been compromised
This is likely a false positive, if chrome is using haveibeenpwned API.
e.g. A pin of 87623103
Hashes to 558B4C37F6E3FF9A5E1115C66CEF0703E3F2ADEE
We get the range from HaveIBeenPwned:
https://api.pwnedpasswords.com/range/558B4
And search for C37F6E3FF9A5E1115C66CEF0703E3F2ADEE
And see it's "Compromised" and seen 3 times before.
In case anyone else was wondering, not all 8 digit pins are "compromised", although many are, and of course an 8 digit pin has limited security in any automatable scenario.
To get an example that was already in the haveibeenpwned dataset, I wrote a quick script:
The "most compromised" I've seen so far is "17385382", in the DB an astonishing 119 times. It would only take a few hours to iterate through all pins and collect stats for all pins.
> not all 8 digit pins are "compromised"
Sure they have been, I can send you a text file with all of them. It's 850MB, but i expect it compresses very well.
There's a reason I put "compromised" in quotes. By that I mean that not all 8 digit numbers are yet flagged in haveibeenpwned.
Of course there's no world in which they're actually a secure password, which is why it's kind of insane to treat them as one.
>17385382
That's a truncated 9 digit pin of a unix timestamp.
Well yeah if you’re enumerating every 8 digit number you’re of course going to get parts of larger numbers.
Seems a stretch... What is special about that time?
2 replies →
I had this constantly the last couple of days. I've been doing some UI mockups in Claude and it includes a password field, and either it puts in a placeholder of like 1234 or I type asdf to test the field. Then as soon as I do anything else Chrome has a fit because "my" password has (obviously) been "pwned."