A breach notice is not a reason to panic — it is a reason to act in the right order. Most damage after breaches comes from delay and from follow-up phishing, both of which you can control.
1. Confirm what happened
Read the provider's official statement (navigate to their site yourself — do not trust emailed links). Note what data was involved: passwords (hashed or plaintext?), card numbers, IDs, addresses, security answers. The response differs by data type.
2. Change the right passwords first
- The breached account's password — immediately.
- Every account that reused it (this is where a password manager's audit view shines).
- If your email was involved and weakly protected, secure it — email resets everything else.
Generate fresh, unique replacements with a random generator, not by tweaking the old one.
3. Kill sessions and tokens
Changing a password does not always sign out existing sessions or invalidate API tokens. Use "sign out of all devices", review connected apps, and revoke anything unfamiliar — especially on email, social and cloud accounts.
4. Harden the account
- Enable or upgrade 2FA (app/key over SMS).
- Refresh recovery emails/phones and security answers.
- If the site supports passkeys, switch — passkeys give attackers nothing reusable to steal.
5. Watch for follow-up scams
Breach news is prime phishing season. Expect emails claiming to be the breached company, "support" calls, and refund scams. Golden rules: navigate manually, never share codes, and treat urgency as a red flag. See How Phishing Attacks Steal Passwords.
6. If identity data leaked
For government IDs, SSN-equivalents or payment cards: contact your bank, consider a credit freeze / fraud alert with your national bureaus, report card numbers for reissue, and document everything. Many jurisdictions give you free monitoring or remediation rights — check the official notice.
7. Reduce the next breach's impact
You cannot stop companies from being breached. You can make each breach boring: unique passwords everywhere, minimal data shared, passkeys where possible, and a manager keeping track. A breach of a site where you are unique-and-random is an inconvenience, not a crisis.
Apply what you learned with our zero-telemetry tools and references:
Put it into practice: run your next password through the local checker — it never leaves your browser.