Guide · Wallet risk · September 2026

The Twelve Words

The single most expensive message in crypto, taken apart line by line.

The message arrives polite.

The logo matches.

The link opens a page that looks exactly like the wallet you already use—the same colours, the same typeface, the same quiet illustration in the corner.

It asks you, calmly, to confirm your recovery phrase so that access can be restored.

That is the entire article, really. Everything that follows simply explains why the request still works so often.

1. What the twelve words actually are

Most people treat their recovery phrase as a password. That single category error is the root of almost every subsequent disaster.

A password guards an account that someone else already holds. Lose the password and you reset it. The account survives.

A recovery phrase is different.

It is the master number from which every one of your private keys is generated. Your wallet takes those twelve (or twenty-four) words, converts them into an extremely large integer, and derives every address you will ever control on every chain the wallet supports—including chains you have not yet used.

The phrase is not a key to a door.

It is the material from which the doors themselves are made.

2. Why nobody legitimate ever asks

Support cannot use it. A wallet provider never holds your funds and therefore cannot move them on your behalf; that is the design. Handing a support agent your phrase would hand them complete control of your money. No competent company permits that request.

A migration cannot require it. Moving to a new contract or a new app version happens on-chain, or by you re-importing the wallet yourself, on a device you control.

An airdrop cannot require it. Sending tokens needs only your public address—the one you paste into forms. Receiving never demands proof that you can spend.

A security check cannot require it. Proving ownership is done by signing a message; the signature confirms control without ever revealing the keys.

A refund cannot require it—least of all a refund for a previous scam.

Every one of those products exists. None of them has ever needed your recovery phrase, because the phrase does not authenticate you. It replaces you.

This is not only our claim. MetaMask's own support documentation states the rule plainly: “if anyone asks for your Secret Recovery Phrase, they are trying to scam you” — a wallet vendor saying, about its own support team, that the request itself is the proof.

3. Five costumes, one request

The stories change. The final sentence does not.

4. Here is one

Read it the way you would at half past eleven at night, on a phone, after being told something is wrong with your money.

This is representative of real campaigns documented by security researchers and wallet vendors. The wording, urgency, invented restrictions, and recovery-phrase request appear repeatedly in phishing messages targeting MetaMask, Trust Wallet, hardware-wallet users, and generic “crypto wallet” recipients. Live versions use different brand names and domains; the underlying request does not change.

5. Why the spelling test stopped working

For two decades people were taught to spot fraud by its seams—broken English, a mismatched logo, a greeting that begins “Dear Customer.”

That advice made sense when producing a convincing page was expensive.

It is now free. Fluent text in any language can be generated in seconds. Copying a website’s exact appearance has never been difficult; the design is public by definition.

A message that looks professional therefore tells you nothing about its legitimacy. It only tells you that someone spent a few minutes.

What has not changed—and cannot change—is what the attacker needs. They need the words. Whatever else they invent, they must eventually ask for them.

Stop grading the presentation. Read the request.

6. Why there is always a clock

Every version of this message contains a deadline: twenty-four hours, end of day, before the account is suspended.

The clock is not there to hurry you. It is there to prevent the single action that reliably collapses the attack: telling another person. Spoken aloud to almost anyone—a friend, a forum, a search engine—the request evaporates. A deadline forces the decision to be made alone.

The deadline is therefore not a detail of the story. It is load-bearing. When you notice one attached to a request for secrets, that observation is itself the finding.

7. Where the phrase should live

Briefly, because the rule is simple.

You type your recovery phrase in exactly one situation: restoring a wallet into software you installed yourself, on a device you control.

Never into a web page.

Never into a form that arrived in a message.

Never into a chat, a support ticket, a spreadsheet, a photograph, a password-manager note, or an AI assistant.

If you use a hardware wallet, the phrase should never be typed into a computer at all after the day you first wrote it down.

8. If you already entered it

Then this section is the only part that matters, and speed matters more than neatness.

On the gas problem, because it catches people at the worst possible moment: moving a token requires the chain’s native coin to pay the fee. If the compromised wallet holds none, you must send some in—and automated sweepers watching the address will often take it within a single block. People try three times, lose the gas three times, and conclude nothing can be done.

Workarounds exist, including bundling the funding and the rescue into one atomic transaction that cannot be interrupted. They are fiddly and chain-specific. If a meaningful amount is at stake, ask someone experienced before burning further attempts.

And the cruellest sequel: people who have just been robbed are often approached within hours by “recovery specialists” who promise to trace and return the funds. They ask for the phrase again, or for an upfront fee. It is the same attack, aimed at the same person, on their worst day. Nobody can reverse a blockchain transaction. Anyone claiming otherwise is selling the second robbery.

9. What a scan can and cannot tell you

Paste a message like the one above into our scanner and it will return FAIL, flagging the seed-phrase request as critical and noting the suspicious link structure.

Here is what it does not do.

• It never visits the link. It examines the address’s shape—brand names in positions that carry no authority, look-alike characters, redirect patterns—but it does not fetch the page. It cannot tell you whether the site at the other end is a clone.
• It cannot see a message you never paste. Most of these arrive when you are tired and in a hurry, which is precisely when nobody checks anything.
• A clean result is not a verdict on the sender. It only means no covered pattern matched.
• It cannot undo anything. Section 8 exists because scanning afterwards is not a remedy.

For this particular attack a scanner is a useful backstop, not the primary defence. The defence is one sentence long, and you already have it.

The rule

Nobody needs your recovery phrase. Not ever. Not for any reason. No matter who they claim to be.

Any message that asks for it is a theft attempt. That is not a heuristic with exceptions; it is the complete rule, and one of the rare security rules that truly has no edge cases.

If you are ever unsure, distrust the deadline first. Then ask someone. That single step ends the attack.

Related: instructions written for an AI rather than for you, and text that renders as nothing. This article is for educational purposes only and is not financial advice. The example message is representative of real campaigns, uses a reserved example domain, and targets no real company.