TL;DR / Summary: When a breach or credential-stuffing wave hits a service you use, rotate that password immediately with a freshly generated secret, check every other site where you reused anything similar, and verify MFA still stands. Speed matters more than writing a perfect incident essay.
Treat reuse as the blast radius
Credential stuffing works because people recycle passwords. If the breached site had a password you also used elsewhere—even with a tiny tweak—assume those other accounts are next.
Your first question is not “was my email in the dump?” Your first question is “where else did this password family appear?”
Password managers that show reused or weak marks earn their keep on days like this. Sort by reuse and start at the top.
Rotate the breached account first
Sign in while you still can. Generate a new long random password that shares no prefix with the old one. Save it in the manager, then change the site password, then sign out other sessions if the site offers that control.
Avoid emotional passwords inspired by the breach headlines. Random beats clever under stress.
Order of operations
- generate and store the new secret
- change the password on the affected site
- revoke active sessions and app passwords
- confirm recovery email and phone still look right
Changing the password while recovery SMS points at an old number leaves a hole open.
Generators like Strong Random Password remove the temptation to invent something memorable while you are rushing through a dozen sites.
Hunt for siblings of the old password
Variants such as Summer2024! and Summer2024!x count as related. Stuffing tools try those patterns. Replace every related string, not only the exact match.
If you used a personal algorithm—pet name plus year plus site initial—retire the algorithm entirely. Replace with unique random values per site.
Related passwords are one incident away from becoming the same incident.
Mark replaced entries in your manager notes with the rotation date so you know the work is done.
MFA is necessary, not sufficient
Enable MFA on the breached site if it was off. Prefer app-based or hardware factors over SMS when both exist.
MFA does not mean you can keep the old password. Session theft and poor MFA implementations still exist; a fresh password shrinks the window.
Review backup codes. If you never stored them, generate and file them now. If you stored them in the same breached notes doc, move them.
Email inboxes are high-value pivots
If the reused password also protected email, rotate email before most other sites. Password-reset links flow through the inbox.
Check forwarding rules and filter rules after a suspected inbox compromise. Attackers hide forwarding quietly.
Inbox items to inspect
- unexpected forwarding addresses
- recent security-alert emails you ignored
- app passwords created for mail clients
Revoke unfamiliar app passwords even if you are not sure—recreating them takes minutes.
Banking and work accounts get priority after email
Financial, payroll, and work SSO accounts outrank streaming and forums. Rotate in that priority even if the breach headline named a gaming site—reuse makes the headline incomplete.
Notify work IT if a work-related password might have been involved. Corporate detection beats silent hope.
Priority is impact, not alphabetical order in the vault.
For joint household accounts, tell the other person which entries changed so they update devices that cached the old password.
Watch for fake “reset now” phishing
Breach news triggers phishing waves that imitate the breached brand. Navigate to sites via your bookmarks or manager launch buttons, not via email links, while you rotate.
Confirm TLS and the domain spelling before pasting a newly generated password into a form. Pasting into a phishing page hands the attacker the fresh secret.
If a call or chat support actor asks you to read the new password aloud, stop. Real support does not need that.
Devices that cached the old password
Phones, TVs, and desktop clients keep old credentials until they fail. After a rotation, open each device that used the account and sign in fresh so you are not locked out during a trip or a livestream.
Mail apps with stored passwords may hammer the server with the old secret and trigger lockouts. Update or remove those profiles the same day.
Browser password stores can re-offer the old value and undo your careful manager update. Delete the stale browser entry so autofill cannot resurrect it.
When you cannot log in to rotate
If stuffing already locked the account, use the official account-recovery path from a bookmarked URL. Generate the replacement password before you finish recovery so you are not tempted to reuse anything in the panic of a reset email.
If recovery fails because the attacker changed the email or phone, contact the provider’s compromised-account channel with identity documents as requested. Do not negotiate with anyone who messages you first claiming to be support.
Finish with a short reuse audit
After the urgent rotations, run the manager’s health check. Clear remaining reuse clusters. Turn on breach monitoring features if you have them.
Write three lines for yourself: what was breached, which accounts you rotated, and whether MFA gaps remain. That note prevents double work when the next headline arrives.
Credential-stuffing days reward people who already generate unique passwords. If you were not one of them yet, this rotation is how you become one—starting with the accounts that share any DNA with the leaked secret.