Except they werenât. Hashes were leaked, which isnât at all the same thing. A sufficiently-strong password stored someplace like 1Password will be largely immune to a hash attack, unless they want to throw the proverbial âkitchen sinkâ at your password. And that would be ONE password, not 71,000.
This is really the core of the discussion.
There are three primary ways for a hacker to compromise your password.
The first is for the password to be stored in cleartext somewhere. Banks, credit card companies, etc. arenât doing that.
The second is for them to run brute-forcing against a hashset. Brute-forcing yields COMMON passwords in real-time, not 50-character 1Password passwords that use uppercase/lowercase letters, numbers, and symbols.
The third is for them to hack the code of the site / organization such that they capture passwords as theyâre being entered.
In the first âcleartextâ scenario, the breach is inevitable, and will be limited to one site as long as youâre using unique passwords. Employees at the site can already steal your freshly-changed password whenever they feel like it.
In the second scenario, the likelihood of your password being compromised is pretty much zero. Nobody is putting in that much effort for your password, and again - thatâs all that effort for YOUR password. Not for a list of 70,000 passwords.
In the third scenario, your password is compromised as soon as itâs changed, no matter how often you change it.
In light of the above considerations, I donât see that this is even relevant. If hackers got your password, and it was a huge 1Password randomized monstrosity, that means that youâre dealing with scenario #1 or #3. In other words, either theyâre using cleartext or their whole codebase is compromised. In either case, you shouldnât use that company for anything that requires true security.
Changing your password on a regular basis really yields no significant benefit.