What a MetaMask recovery phrase actually controls

MetaMask calls it a Secret Recovery Phrase. Other wallets call the same object a seed phrase, a mnemonic, or a backup phrase. The naming differs; the object does not. It is a BIP-39 mnemonic, and it is the root from which your accounts are derived.

What follows is the part that tends to be skipped: the phrase does not cover everything you see in the extension, and the gaps are where people lose things.

What it does control

Every account MetaMask derived for you from that phrase — the first one, and each additional account you created by clicking “Add account”. They come from the same root, in a fixed order, along a standard derivation path. Restore the phrase into a fresh installation and those accounts reappear in the same sequence.

Because the derivation is standard rather than proprietary, the phrase is not locked to MetaMask. The same words restore the same accounts in other compatible wallets. That portability is a genuine feature, and it is also why the phrase alone is sufficient for anyone who obtains it.

What it does not restore

Accounts you imported by private key. This is the costly one. If you pasted a private key into MetaMask to add an account, that account was never derived from your recovery phrase — it was attached alongside it. Restoring the phrase on a new machine brings back the derived accounts and silently leaves the imported one behind. Nothing warns you at restore time, because from the wallet’s perspective nothing is missing. People discover this when the machine is already gone.

Custom networks you added. Network entries are local configuration. The accounts and their balances exist on those chains regardless, but a restored wallet will not know the networks exist until you add them again.

Tokens you imported. Same principle. A token balance lives on-chain and is unaffected by which wallet is looking at it, but the list of tokens MetaMask displays is a local preference. A restored wallet can look empty while holding everything, which is alarming and routinely mistaken for theft.

The pattern: the phrase restores ownership, not configuration. Anything you typed into the interface is configuration.

The failure modes that actually lose funds

Being asked for it. No legitimate support process — MetaMask’s or anyone else’s — requires your recovery phrase. There is no diagnostic that needs it, no verification step, no migration tool. A request for it is the attack, in every case, without exception. It is worth holding that as an absolute rather than a guideline, because the convincing versions do not look like scams.

Storing it somewhere that syncs. A photograph in a cloud-backed camera roll, a note in an account protected by a password you reuse, a screenshot. Each turns custody of the funds into custody of whichever account holds the backup, usually one secured far less carefully.

Assuming the password helps. The MetaMask password encrypts the local vault on that device. It is not a second factor on the phrase. If the phrase is out, the password is irrelevant — a point covered in seed phrases, private keys and passwords are not the same.

If it has been exposed

You cannot rotate a recovery phrase. There is no revocation, and no support path. The only response is migration: create a new wallet with a new phrase, on a device you have reason to trust, and move assets to the new accounts.

Move quickly and expect to be racing software rather than a person. Compromised phrases are swept by automated tooling, and funds arriving at a known-compromised address can be taken faster than a human could react.

Two details worth planning for before you are under pressure. Moving tokens costs gas in the chain’s native asset, so an account drained of its ETH cannot move its remaining tokens — deal with that constraint first. And if you hold an imported account, remember it is not covered by the phrase at all; it needs its own key handled separately.