Most of us who write software assume we’re the careful ones. We don’t click sketchy links, we know what a phishing email looks like, we lecture other people about password hygiene.
Then I ran my own email through a breach database — and that confidence didn’t survive the night.
Four breaches. An old forum. A dead SaaS trial. A food app. And one password I was still actively using, sitting in leak dumps anyone can download.
If it can happen to someone who reads about this for fun, it can happen to anyone shipping code today.
You’re not breached because you failed
Here’s the part worth internalizing: most exposure has nothing to do with your habits. A service you trusted got compromised, and your email and password ended up in a combo list resold for almost nothing.
Your 2FA discipline didn’t matter in that moment. Their database did.
The real threat is credential stuffing
Leaked credentials aren’t dangerous because of one site. They’re dangerous because attackers replay them everywhere, automatically.
The pattern is depressingly simple:
Grab a leaked email-and-password combo list
Point a bot at hundreds of login endpoints
Rely on the fact that most people reuse passwords
Harvest whatever unlocks
No zero-day. No clever exploit. Just reused passwords and automation. We build the login forms these attacks hammer — so we should be the last people reusing credentials.
What I changed in 48 hours
None of it is advanced. It’s the stuff we tell users to do and then skip ourselves.
Audit your exposure first. Find out where you already leaked before changing anything. If you’ve never done this, I wrote a plain-English walkthrough on how to check if your email has been in a data breach — start there so you’re fixing real problems, not guessing.
Kill password reuse — email account first. Your inbox is the root credential. Every password-reset link lands there. Rotate it before anything else.
Let a password manager generate your secrets. Humans produce low-entropy, patterned passwords that modern hardware cracks fast. I stopped inventing them — now I don’t know a single one of mine, which is the point.
Enable 2FA (and move toward passkeys where you can). Highest-leverage control on the list. Even with a valid password, an attacker stalls without the second factor. Prefer TOTP or passkeys over SMS.
Re-check on a schedule. Breaches are continuous. A quarterly re-check catches new exposure while it’s still fixable.
The mental model that stuck
A leaked 2019 password only hurts you if it still works in 2026.
Security isn’t about keeping your data off the internet — that ship sailed. It’s about making the pieces already out there useless. Unique secrets plus a second factor break the replay chain credential stuffing depends on.
We spend our careers protecting other people’s accounts. Worth spending one evening on our own.
Run the check tonight. Best case, you’re clean. Worst case, you catch it before someone else does.
I write plain-English breakdowns on security, privacy, and staying safe online at Global Insightly.
Top comments (0)