Learn/PasswordsFoundation of Trust

Password Manager Breach: What to Change First, in Order

A password manager breach notice can ask you to change everything at once. Here is the order that matters: confirm it, lock email, then money, then 2FA and passkeys.

Signed by M·
Open laptop on a dark wooden desk at night beside a paper notebook with a short numbered list and a pen
What should I do first after a password manager breach notice?

After a password manager breach notice, confirm the notice on the vendor's own site, then secure your email account first, then banking and payment accounts, then any account whose two-factor codes or passkeys were stored in the same vault. Work from a list so nothing is changed twice or skipped.

A password manager breach notice lands differently from any other security email. The vendor is not telling you one account is at risk. It is telling you the box that holds every account might be. The natural reaction is to change everything tonight, in whatever order the list scrolls. That order is the wrong one.

On November 3, 2026, customers of the mSecure password manager received exactly this kind of message. A copy posted on mSecure's own support forum says the developer "recently learned of suspicious activity," launched an investigation and brought in outside experts. It then recommends steps that "may include changing passwords, resetting or re-enrolling two-factor authentication methods, or removing existing passkeys." That first notice did not say what happened or what was reached.

Updated November 16, 2026: mSeven support has since sent customers a fuller reply, which they posted in full on the same forum. It says "an unauthorized actor acquired an encrypted copy of a database containing information belonging to current and former users," that mSeven "has no evidence that the unauthorized actor has accessed the confidential information stored within the database," and that "this issue only pertains to users that were synching with the mSecure Cloud." It still recommends changing your master password and vital stored passwords, resetting two-factor and replacing passkeys. If you synced with mSecure Cloud, the order below is for you.

This page gives you the order. Whatever vault you use, a password manager incident is a triage problem. Some accounts can reset other accounts. Some hold money. Some stored their second factor in the same vault as their password. Those come first, and the rest can wait an evening. The Foundation of Trust starts from the same idea: know which keys open which doors before you need to change the locks.

Why a breach needs an order, not a panic

A typical vault holds hundreds of logins. Changing them in alphabetical order spends your first hour on a forum account while your email, the account that can reset everything else, still has the old password.

Standards already treat exposure as a reason to change, not a matter of taste. NIST's digital identity guidelines (SP 800-63B) tell services not to force routine password changes, but say a service must force a change when there is evidence a password has been compromised. A vague notice from a password manager is not proof that your passwords were read. It is reason enough to act as if the important ones were.

A list is the tool. Before you change anything, open a notebook or a plain text file on a device you trust and write down your accounts in four groups: accounts that reset others (email, phone carrier), accounts that move money, accounts whose two-factor codes or passkeys lived in the vault, and everything else. If you already made a digital emergency plan, it is most of this list. Tick each line as you finish it. A password manager breach is a long evening, and the list is what stops it from turning into two.

A password manager breach checklist, in the order that matters

Work from a laptop or desktop you control, not from a shared or unknown machine. Keep your phone nearby for sign-in prompts. Change one account fully, confirm you can sign in again, then move to the next line.

Confirm the breach notice is real

Incident emails are copied by attackers within hours, because a message that says "sign in now to protect your vault" is a perfect lure. Do not use the links in the email. Open the vendor's website or app yourself and look for the same notice. If the vendor has published nothing yet, treat the email's advice as reasonable but click nothing in it.

Then decide where your new passwords will live. If you plan to keep using the same vault, change its own master password first. If you plan to leave, read the last section before you rotate anything, so the new passwords never enter the old vault.

Secure email and the phone account first

Email resets almost everything else, so a password manager incident starts there. Give the email account a new, long, unique password, review its recovery phone and recovery address, and sign out other sessions if the service offers it. Do the same for your mobile carrier account, because a texted reset code goes wherever the number goes.

The EFF's guide to strong passwords explains why each password should be long and unique. Uniqueness is what keeps one exposed password from opening a second account.

Then money, work and the accounts that hold your files

Next come banks, brokerages, payment apps and cards saved in shopping accounts. Then the accounts your work depends on, and the cloud accounts that hold your photos and documents. Change the password, check the account's recovery settings, and look at recent activity while you are there. If anything looks wrong, call the institution using the number on its own website or card, not a number from an email.

Only then move to the long tail. Old forum accounts and one-time shop logins matter less, but they still deserve new passwords, because reused passwords are how one leak becomes three.

After the password manager breach: two-factor, passkeys and where the vault lives

Passwords are the visible part of the work. The quieter part is everything else the vault held.

Re-enroll two-factor that lived in the same vault

Many password managers can store authenticator seeds, the secret behind the six-digit codes. That is convenient, and after a password manager breach it is the reason the notice mentions two-factor at all. If one vault held both the password and the code generator, both factors may be exposed together.

For each such account, turn two-factor off and on again so the service issues a new seed, and store that seed somewhere other than the old vault, such as a separate authenticator app or a hardware key. Save the new backup codes offline.

Replace passkeys without locking yourself out

Passkeys resist phishing because each one is bound to the site that created it, as the FIDO Alliance explains. A passkey stored in a vault is still a credential in that vault, which is why the mSecure notice mentions removing them. You do not "change" a passkey. You create a new one and delete the old one.

Order matters here. On each account, first add a new passkey on your device or confirm another working sign-in method, sign out and back in to prove it works, and only then remove the passkey that lived in the old vault. Sign in with MATA works the same way on purpose: the key is on your device, so there is no vendor copy to rotate.

Decide where the vault lives next

Moving to another manager does not undo a breach. It changes what the next incident can reach. If you leave, move first and rotate second, so the new passwords are only ever saved in the new vault. A CSV export writes every password to disk in plain text, so import it straight away and delete the file.

MATA's Password Manager is built around that choice. Its product page says credentials are sealed with AES-256-GCM using a key derived from your passphrase with Argon2id, that the vault syncs between your own devices, and that MATA does not hold a copy of the key. That design narrows what a vendor-side incident can expose. It does not protect a device someone else controls, and it does not replace the checklist above. The import guide covers the CSV step for each major vault, and Friends Backup covers recovery without a vendor reset. If you want the whole sequence, the Freedom Guide puts it in order, and you can create a MATA account when you are ready. Trust, Security, Incentive: the key stays with you.

FAQ

Short answers already in this article.

Should I change every password after a password manager incident?

Plan to, but not all at once. Change the accounts that can reset others first: email, phone carrier, banking. Then work down the list. Even when a vendor says the stolen copy was encrypted, as mSeven did for mSecure Cloud users, it may still tell you to change the master password and vital stored passwords.

Why do two-factor codes matter after a vault breach?

If the vault also held your authenticator seeds, the password and the second factor sat in one place. Re-enroll two-factor on those accounts so the new seed lives somewhere the old vault never touched.

Can I just delete my passkeys after a password manager breach?

Add a new passkey or another working sign-in method on each account first, then remove the old passkey. Deleting first can lock you out of an account you were trying to protect.

How do I know a breach email from my password manager is real?

Do not click its links. Open the vendor's website or app yourself and look for the same notice there. Attackers copy real incident emails, and an urgent request to sign in is exactly what a phishing message looks like.

Does moving to MATA undo a password manager breach?

No. Moving vaults does not un-expose anything. MATA's password manager keeps its decryption key on your device, which narrows what a vendor-side incident can reach next time. The rotation work still has to happen.