Guide

Wallet phishing and seed phrase scams: What to check

Distinguish a request for your recovery words, a stranger's leaked phrase and a suspicious wallet approval. Each needs a different check.

By Jordan Fraser21 min readPublished Oct 21, 2026

In this guide · 10 sections
  1. Identify which request you are facing
  2. How does a phishing approach create a reason to act?
  3. Know when a recovery phrase is actually used
  4. How do you reach genuine wallet software and support?
  5. Leave a stranger’s leaked phrase alone
  6. Check wallet approvals even when no words are requested
  7. How should you prepare a backup without exposing it?
  8. Act according to what was exposed
  9. Worked examples: which decision comes next?
  10. Questions about wallet phishing

Wallet phishing and seed phrase scams do not all ask for the same thing. Someone may request your recovery words, offer a stranger’s supposed leaked wallet or persuade you to approve a transaction. MetaMask’s security guidance explains why recovery words control wallet access and must not be shared with someone claiming to be support.

Start with what the request would expose. If you have already shared words, installed suspicious software or approved something you do not recognize, stop interacting with that source and use your wallet provider’s verified guidance.

The confusing part is that genuine wallet software also contains words such as restore, import and connect. A familiar label does not tell you whether you reached the right application or whether the action matches your intention. This guide separates those decisions. It explains which information is secret, how to approach a restoration you actually need and how to describe an incident without exposing more access while asking for help.

Use the section matching what happened, not the label attached by the sender. Reading an email, installing an application, revealing recovery words and confirming a wallet prompt are distinct events. If several happened, record each one. You can stop before the next step even when the previous step seemed harmless.

Identify which request you are facing

A request for recovery words, a leaked phrase and a spending permission are different situations. Treat the wording on the page as a claim to verify, not an instruction you must follow.

RequestWhat to stopCheck
Enter your words to verify, synchronize or repair a walletDo not submit them to the page or personWhether your provider documents that exact process in its genuine app or device
Use a stranger’s leaked phrase to access a balanceDo not import it, fund it or install suggested softwareYour own device security if you already opened or installed something
Approve a wallet prompt without sharing wordsReject a request whose purpose you cannot explainThe site, recipient or contract, asset and permission shown by your wallet

This table is a checking aid, not a detector. You do not need to complete a suspicious request to establish whether it is safe.

Identify the information before you share it

A public receiving address identifies where another person can send assets. It is not the secret used to control the account. Ethereum’s wallet guide distinguishes the receiving address from the keys that control access. Sharing an address does not mean you should also reveal a backup, export a key or sign a request. If someone asks you to prove the address is yours, first establish what proof they actually need and why.

MetaMask’s explanation of recovery words and private keys distinguishes the wallet’s recovery phrase from a private key controlling an individual account. Both are secret. A request to export a private key is not made acceptable by avoiding the words seed phrase. Read the field label and the surrounding explanation, and stop if you are being asked to give another person control rather than identify an account.

A password can serve a different role depending on the setup. MetaMask’s current security guidance explains the distinction between phrase based setup and a connected Google or Apple account. With a connected account, that login and the MetaMask password work together to access the wallet. MetaMask says support will not ask for the password. Do not assume a password request is harmless just because nobody asked for recovery words.

For your own notes, use the exact type of information requested: receiving address, app password, private key, recovery phrase or document. Avoid the broad description “wallet details.” It can hide the difference between sharing a destination and disclosing a secret. You should be able to tell a support representative what category was exposed without supplying the secret itself.

How does a phishing approach create a reason to act?

Look for the gap between the problem described and the access requested. A message may claim there is a security issue, but that claim does not explain why a stranger needs your backup. Evaluate the requested action separately from the urgency or technical vocabulary used to justify it.

Trezor warns about impersonated support and device deactivation threats. It says it cannot remotely deactivate a Trezor device and directs worried users to its official support channels. This is a specific statement about Trezor hardware. It should not be turned into a claim that every hosted exchange account or online service is incapable of being restricted.

That distinction matters when a message mixes different products. A trading account, a hardware device and an application used to view a wallet are not the same thing. Ask which component supposedly has the problem. If the explanation moves between them without showing how the requested action helps, do not fill in the missing reasoning on the sender’s behalf.

A convincing support reference still needs checking

Ledger documents a scheme involving an unsolicited support ticket confirmation followed by an impersonator’s call. The genuine looking ticket message can make the separate caller appear credible. Ledger also describes fake application errors that lead to demands for recovery words. Neither example means every error or support email is fraudulent; it shows why the surrounding contact needs its own check.

When a support reference surprises you, open a fresh conversation through the provider’s independently established channel. Explain that you did not initiate the contact and ask about the reference. Do not let the caller conduct this check for you, and do not treat their ability to repeat a reference number as permission to handle your secrets.

You can ask for written instructions without agreeing to perform them. Save the description of the alleged problem and the action requested, then compare it with the genuine provider’s guidance. If the contact insists that only they can explain the instructions, leave the action pending. An unanswered technical question is a reason to seek clarification, not a reason to press confirm.

Know when a recovery phrase is actually used

Recovery words can restore wallet access, so entering them during a genuine restoration is different from giving them to a support agent. The safe procedure depends on the wallet and how it was set up.

For example, MetaMask documents phrase entry within its wallet restoration process. That does not authorize a website form reached through a message, advertisement or supposed support reply. Open the provider’s official instructions yourself and confirm that you are using its genuine software before proceeding.

Hardware wallet instructions can differ. Trezor says its support team will not ask for a wallet backup and warns against entering it unless the Trezor device prompts you. Follow the instructions for your exact device rather than transferring steps from another wallet.

Before restoring, resolve these questions:

  1. Did you initiate a restoration for a reason you understand, or did an unsolicited message create the urgency?
  2. Did you obtain the wallet software and instructions independently of that message?
  3. Does the process match the provider’s documentation for your setup?

If any answer is unclear, pause. Do not send recovery words, private keys or pictures of a backup to someone offering to check them. A public wallet address and a secret recovery phrase are not interchangeable evidence.

Match the recovery method to your existing setup

Before changing anything, identify the product, device and setup method you used originally. Were you using a hardware wallet, a wallet created from recovery words or an account connected through a supported login service? Keep this description free of secrets. It helps you choose the relevant official instructions instead of following the first guide that uses the same brand name.

MetaMask’s restoration documentation also explains that separately imported accounts may need to be added again. An incomplete account view after restoration is therefore not, by itself, evidence that a stranger’s recovery service is needed. Check the provider’s account restoration guidance before following instructions to reset the wallet again. Do not erase an existing installation until you understand the backup requirements for the accounts involved.

Give yourself room to read the whole official procedure before starting. Identify where it expects you to enter information and which device should display the request. If a step on your screen differs materially from the documented process, stop at that point. Record the nonsecret difference, such as an unexpected website form, rather than trying additional words or another person’s suggested tool.

A passphrase is not simply another name for the backup

Trezor describes its optional passphrase feature as a way to access an additional wallet using the backup and the exact passphrase. A different entry can open a different wallet. Trezor warns that a lost passphrase cannot be recovered. This advanced feature has its own requirements; it is not a universal instruction to add a word during restoration.

If you previously used a passphrase, say so when seeking guidance without disclosing it. If you did not, do not introduce one merely because a chat contact says it will repair a balance. Keep setup changes separate from diagnosing an unexpected screen. Changing several things at once makes it harder to describe which step produced the result you are trying to understand.

How do you reach genuine wallet software and support?

Establish the provider’s destination independently before downloading software or entering wallet information. The path by which you arrive is part of the check. A site reached through an unsolicited message has not become independent evidence merely because it contains a help centre or a download button.

Search results and advertisements

Trezor’s March 2026 phishing article describes paid search links to fake sites. Search position is not proof that a result belongs to the wallet provider. The article also describes copied profiles and false update messages. These are documented examples, not a claim that every advertisement or update notice is malicious.

If you used search to find help, compare the destination with a provider address you established independently. Check the complete domain before you enter information. A familiar word in a page title, logo or URL path is not a substitute for that comparison. Do not rely on the page’s own statement that it is official.

Once the destination is established, keep a bookmark for later visits. Review the destination when using it rather than treating the bookmark’s name as evidence. For a download, follow the provider’s own instructions for obtaining and checking its application. Do not replace that route with a file attached to a support message because the person says it is a faster fix.

QR codes and physical letters

Ledger’s phishing campaign record includes letters directing recipients through a QR code or website to a recovery phrase request. A printed letter changes the delivery method, not the need to verify the request. A code that opens a page has not established who operates that page.

If a code is supposed to resolve a wallet security issue, find the provider’s guidance separately before using the destination. Do not move from a larger screen to a phone simply because a letter asks you to scan. Read what the requested action would expose. The same rule applies whether the instruction arrived on paper, in a message or beside a video.

Keep help requests narrowly focused

A useful initial support message describes the product, the problem and the action you already took. For example, you can say that you reached an unfamiliar form after selecting a search result and stopped before entering recovery words. You do not need to attach a backup to explain that sequence.

If a screenshot would help, inspect the entire image before sharing it. Keep backup words, keys, passwords and unrelated personal information out of view. Prefer describing a sensitive screen in words over creating an image that contains the secret. Ask what nonsecret information support needs rather than sending an unrestricted account or device recording.

Leave a stranger’s leaked phrase alone

A phrase that appears accidentally exposed can be part of a deliberate trap. Do not import someone else’s wallet, send funds to it or install a special app to reach the advertised balance.

In research published on 30 July 2024, Kaspersky investigated a scheme that staged leaked wallet information and eventually steered visitors toward a malicious wallet application. The apparent opportunity was the lure. This is one documented mechanism, not a claim that every leaked phrase scam follows the same sequence.

A screenshot showing money does not establish that the offer is genuine or that you are entitled to those funds. Nor does a convincing wallet display justify installing software supplied by the same stranger. Leave the offer alone rather than trying a small payment to see what happens.

If you already downloaded an app from the approach, tell your verified support contact what was installed. Do not move your own wallet secrets into that app while investigating it.

Why apparent access is not a reason to investigate further

The decision is not whether the stranger’s displayed balance is large enough to justify a small experiment. The decision is whether you have a legitimate reason to access that wallet and trust the software involved. The apparent presence of recovery words answers neither question. It also does not establish what else a recommended application would do on your device.

Treat the instruction to install something special as a separate request. Do not let the earlier curiosity decide that later action automatically. If your ordinary wallet cannot interpret somebody else’s supposed backup, that is not a problem you need to solve. There is no need to test converters, contact the poster or deposit funds to continue the investigation.

When helping another person with a leaked phrase approach, focus on their own exposure. Ask whether they installed anything, entered any of their own secrets or sent money. Do not ask them to demonstrate the offer by opening it again. The useful outcome is a clear account of what happened to their device or accounts, not access to the advertised wallet.

Check wallet approvals even when no words are requested

Keeping your recovery phrase private does not protect against every permission you grant. A token approval can let an application move a particular token from your wallet. Legitimate applications also use approvals, so the task is to understand the specific request, not label every approval fraudulent.

Read the wallet’s displayed action, asset, contract and spending limit where provided. Compare them with the action you meant to take. Reject an unexpected prompt or one you cannot interpret; return to the provider’s documentation rather than relying on the requesting site’s reassurance.

Disconnecting is not the same as revoking. MetaMask explains that disconnecting a site leaves existing token approvals in place. Closing the tab or clearing browser history should not be treated as evidence that a spending permission is gone.

Not every signature is a token approval, and removing one approval does not fix an exposed recovery phrase. Our wallet drainer case study examines the permission mechanism separately. If the prompt came from an investment website, also check its identity using the fake platform verification guide.

Compare the prompt with your intended task

Write down what you intended to do before interpreting a confusing prompt. If the task was to read a balance, ask why the next step appears to involve spending permission. If you meant to receive an asset, ask why you are being asked to authorize a different action. This comparison does not identify every malicious request, but it makes a mismatch easier to describe to verified support.

Do not allow a website’s label to replace the information shown by the wallet. Keep the claimed purpose and the actual request side by side. If the wallet cannot present enough information for you to understand the action, decline it while you investigate. A prompt does not become appropriate merely because it can be technically confirmed.

You can record that you declined an unclear request without deciding exactly what attack it might have contained. That is sufficient for choosing the next source of guidance. The drainer guide covers the deeper permission questions; this article’s purpose is to stop phrase protection from becoming a false assumption that all other actions are safe.

How should you prepare a backup without exposing it?

Use the provider’s documented backup process for the setup you actually have. Keep the purpose clear: a backup supports your future access. It is not something you submit to an unfamiliar person to certify an account, collect a reward or resolve an unsolicited warning.

Trezor’s backup guidance says to avoid digital copies, check the words and their order, and protect the record from theft and damage. Follow those instructions for a Trezor wallet backup. Do not generalise them into a description of every product’s recovery architecture; a wallet with a documented account login method may work differently.

Decide how you will find the instructions later

Keep a separate, nonsecret note identifying the wallet product and the official documentation you used. Record whether the setup involves a hardware device, a phrase you hold or a supported account login. This note should not contain the backup itself. Its purpose is to help you locate the right process when you are under pressure or replacing a device.

Consider the situation in which you would need that note. If your phone stopped working, would you know which provider’s documentation to consult? If a family member helped you find it, could they do so without seeing your secrets? These questions let you improve the organisation of your records without creating extra copies of the recovery material.

Check preparation before deleting or resetting

An instruction to reset an application deserves a pause. Establish what the provider says will be removed and how you would restore the relevant accounts afterwards. Do not assume that one visible backup necessarily covers everything imported into an application. Use the account specific guidance rather than a generic promise that everything will return after reinstalling.

Avoid experimenting with recovery on an unfamiliar website just to test whether your written record works. A practice run should use the provider’s documented verification method for your exact product, if one is available. If you do not understand the method, resolve that question before exposing information or changing the working setup.

Keep convenience changes outside an incident

Do not redesign your backup arrangements while an unverified person is directing the process. A decision about storage, additional recovery features or another wallet should be made with time to understand its consequences. During a suspicious interaction, first identify what was exposed and consult the corresponding incident guidance.

When you later review the arrangement, separate two questions: can you recover access, and who else could obtain the recovery material? A record you cannot locate fails the first purpose; unnecessary copies create additional places to consider for the second. Use the provider’s guidance to address both rather than adopting a stranger’s promised universal solution.

Act according to what was exposed

If you shared recovery words, treat the associated wallet as compromised. MetaMask’s incident guidance describes a new wallet and warns against adding fee funds when an automated sweeper may be present. Do not improvise a rescue by sending more crypto into the exposed wallet.

If you signed a suspicious request, preserve its transaction details and use verified guidance to identify the permission involved. Record what you did, without putting recovery words into screenshots or support messages.

For Canadian reporting routes, account security and a private evidence checklist, use what to do after a crypto scam. If you have not interacted and only need to assess the approach, the Canadian scam overview covers the broader warning signs.

You only read a message or opened a page

Record that limited interaction accurately. Do not report that you shared a phrase if you did not, but do not assume that closing the page is a full device assessment either. Note whether anything was downloaded, installed, typed or approved. If you are uncertain, say which part you cannot reconstruct rather than reopening the suspicious page to repeat it.

Decline subsequent prompts and reach the provider independently. Keep the public website address and the message that brought you there if you can do so without further interaction. A screenshot of the instruction can be useful only if it excludes secrets. You do not need to continue until the page produces a more obvious demand.

You entered a password or revealed recovery material

Identify the information involved and the setup it belongs to. A password incident needs the relevant account security instructions; disclosed recovery words require the compromised wallet path. If both happened, explain both. Do not assume that addressing one cancels the other exposure.

For a disclosed phrase, the key question is which wallet and associated accounts the phrase controls, not whether the suspicious page reported success. Follow the provider’s incident instructions promptly. Tell verified support about other relevant actions, such as installing an application or permitting remote assistance, without sending the phrase for inspection.

If you pasted words into a suspicious field but are unsure whether you submitted them, do not rely on that uncertainty as protection. Describe exactly what you did when seeking help. Avoid the unsupported claim that the page definitely captured them or definitely could not have done so. The uncertainty itself should be part of the response decision.

You installed software or cannot identify the action

Use a separate trusted device to locate assistance when the device involved may be compromised. Keep the name of the application, where it came from and the approximate sequence of installation and wallet actions. Do not import your own wallet into the questionable software while checking whether it works.

The MetaMask incident page identifies malicious software and fake extensions among possible causes of compromise. Its guidance also cautions against removing an installation without the recovery material needed to regain access. Device investigation and wallet recovery are related tasks, but deleting an application is not proof that every exposure has been resolved.

If you need technical help, explain the software concern at the outset. A helper looking only at an account transaction may otherwise miss the fact that an unfamiliar application was installed first. Keep your incident notes private and use the reporting guide for the broader record and Canadian reporting steps.

Worked examples: which decision comes next?

These examples are hypothetical. They illustrate how to choose a question or response path, not tests of a named service or predictions of what a scammer will do.

A restore screen appears after a warning message

You receive a warning and follow its link to a form asking for recovery words. Your wallet was working before the message arrived. The next question is not which order to type the words in. It is why a restoration is needed and whether this is the genuine provider’s process. Leave the form, open the official instructions independently and check the stated problem without giving the message sender access.

A friend shares an apparent wallet leak

A friend sends a screenshot containing somebody else’s words and a large balance. They suggest importing it to see whether it is real. The next decision concerns your own device and software, not the size of the displayed balance. Decline the experiment. If your friend already installed an application, help them describe that exposure and find verified assistance without asking to see or reuse any secrets.

A claim page asks for a wallet approval

You expected to read eligibility information but receive a request that appears to grant token access. No recovery words have been requested. The useful comparison is between the task you intended and the permission displayed, not between this page and a typical phrase theft form. Decline the unclear request and use the permission guide to understand it. Keeping the backup private does not answer the separate approval question.

Questions about wallet phishing

Will legitimate support ask for my seed phrase?

MetaMask and Trezor explicitly say not to share recovery words with support. A wallet restoration you initiate in genuine software or on your device is a separate process. Check your provider’s documentation before entering anything.

Is a wallet safe if I changed its password after sharing the phrase?

No. Changing an app password does not change the exposed recovery words. Treat the phrase as compromised and follow the wallet provider’s incident instructions.

Can I lose tokens without revealing my seed phrase?

Yes. A malicious token approval can provide spending access while your recovery words remain private. Review what you authorize as well as where you store your backup.

Should I import a leaked phrase just to check the balance?

No. Leave someone else’s apparent wallet access alone. Do not install recommended software or send a test payment to investigate the offer. If you already interacted, focus on protecting your own accounts and device.

Can I share my public address with support?

A receiving address is different from a private key or recovery phrase. Share only the nonsecret information relevant to the support question and verify the support destination first. Do not attach a full account screenshot merely because an address is requested. Review what else the image reveals before sending it.

Should I send only part of my recovery phrase for checking?

Do not send selected words, an incomplete photograph or clues to a supposed support agent. You do not need to calculate whether a particular fragment would be enough to recover a wallet before declining the request. Explain the problem without disclosing any of the recovery material, then follow the provider’s genuine guidance.

Does a hardware wallet make a phrase request legitimate?

No. Hardware ownership does not authenticate an email, website or caller. Follow the instructions for the exact device and verify where information should be entered. The provider’s documented restoration process is different from a person asking you to disclose the backup in a chat or online form.

Does adding another account fix an exposed recovery phrase?

Do not assume that a new account label creates independent recovery material. MetaMask distinguishes separate recovery phrases and the accounts associated with each. For an exposed phrase, follow the compromised wallet process rather than simply renaming an account or importing the same phrase into another application.

Before acting, make sure you understand what the provider means by wallet and account in that procedure. The distinction matters because a familiar interface can display several accounts together. If you cannot tell which backup controls the account involved, ask the provider how to identify that relationship without sharing the backup. Avoid moving assets based solely on a different name appearing in the account selector.

What if I created the wallet with a Google or Apple login?

Use the documentation for that setup instead of following an unrelated phrase restoration tutorial. MetaMask describes a connected account and wallet password working together, with an associated recovery phrase. Tell verified support which method you used, without sharing passwords or recovery material. Do not convert the setup during an unsolicited support conversation simply because a stranger tells you to.

Evidence

Sources and further reading