If you suspect that an NFT wallet has been phished, the order of your actions matters. This checklist explains how to contain the compromise, protect assets that remain, document what happened, and migrate safely to a replacement wallet without creating new signing risks.
Overview
NFT wallet recovery after phishing is usually not about restoring a compromised wallet to a trustworthy state. It is about deciding what has been exposed, stopping avoidable losses, and moving any remaining assets to a wallet with a clean security boundary. A wallet may still display its NFTs even after its recovery phrase has been copied, and a wallet with no visible loss may still have dangerous approvals or active sessions.
First, separate the affected wallet from the replacement wallet. Do not create the replacement account by importing the old recovery phrase, and do not enter the old phrase into a website, support form, or browser extension. If the phrase or private key was exposed, assume that account is permanently unsafe. A hardware wallet does not repair a compromised phrase if that phrase is later imported into another device.
Use a second, trusted device for the replacement wallet where practical. Keep the new recovery phrase offline, write it down carefully, and never photograph, email, or store it in a cloud note. The new wallet should be used only after its address has been checked character by character or through a trusted address-book process.
Before taking action, preserve evidence. Record wallet addresses, chain names, transaction hashes, collection and token identifiers, suspicious URLs, screenshots, dates, and the sequence of events. This record helps with marketplace reports, wallet-provider support, tax records, and any applicable law-enforcement or fraud report. It does not guarantee that stolen NFTs or funds can be recovered.
Checklist by scenario
1. The recovery phrase or private key may be exposed
- Stop signing transactions from the affected wallet.
- Use a trusted device to create a completely new wallet with a new recovery phrase.
- Write down the new address and confirm the network before sending anything.
- Prioritize assets that remain, beginning with high-value or irreplaceable NFTs and then relevant tokens needed for transaction fees.
- Send assets directly to the new address using small test transfers when the value or chain makes that sensible.
- After migration, treat the old wallet as watch-only. Do not reconnect it to marketplaces or attempt routine trading from it.
If an attacker is actively draining the wallet, speed and accuracy matter. Avoid repeated experimental transactions. Prepare the destination address and transaction plan first, then use a trusted wallet interface. If the remaining asset is held by a contract, on a different chain, or behind a marketplace listing, obtain specialist advice before signing an unfamiliar transaction.
2. A malicious approval or operator permission was granted
An approval can allow a contract or operator to move certain tokens or NFTs without another conventional transfer prompt. The exact remedy depends on the chain, token standard, contract, and wallet interface. Stop using the affected wallet until you understand the permission.
- Identify the contract and approval transaction in a reputable chain explorer.
- Use a reputable wallet approval revoke tool or the relevant chain-native method, checking the contract and network before confirming.
- Do not assume that disconnecting a website revokes an on-chain approval; connection sessions and token permissions are different controls.
- After revocation, inspect the wallet again and consider migrating remaining assets if the seed phrase or private key may also be exposed.
Revoking an approval can require a transaction fee and may not address other permissions, signatures, or compromised credentials. Review each relevant chain separately.
3. NFTs or tokens have already been drained
- Do not send more funds to the drained wallet in an attempt to “unlock” or recover assets.
- Record the theft transaction, destination address, token identifiers, collection contract, and timestamps.
- Notify the relevant marketplace, collection team, wallet provider, and chain or platform reporting channel using official contact details found independently.
- Ask whether the platform has a current process for reporting stolen assets, but do not assume that a report will reverse an on-chain transfer.
- Review tax and accounting records with a qualified adviser if the loss affects a filing or business inventory.
Be cautious of anyone promising recovery for an upfront payment or requesting your recovery phrase, private key, remote access, or a “verification” transaction. Recovery scams often target people immediately after a wallet compromise.
4. A phishing site was used, but no transaction was signed
Do not conclude that the wallet is safe solely because a transaction does not appear on-chain. If the recovery phrase or private key was entered, follow the exposed-credential procedure above. If only a website connection was made, disconnect the site, review active sessions, check approvals, and inspect recent signing activity. Continue monitoring the wallet for unfamiliar transactions and do not revisit the suspicious page.
5. The device, browser, or extension may be infected
Stop using the device for wallet operations. Do not enter a new recovery phrase on a device you do not trust. Update or reinstall the operating system and wallet software only through official sources, or use a separate clean device. Change passwords for related email and marketplace accounts from a trusted device, enable appropriate multifactor authentication, and review email forwarding rules and active sessions. If malware or remote access is suspected, professional incident-response help may be more appropriate than repeated wallet reinstalls.
What to double-check before migration
Migration errors can turn a phishing incident into a second loss. Use this pre-send inventory for every asset:
- Network: Confirm whether the NFT is on Ethereum, Polygon, Base, Solana, or another supported chain. A correct-looking address on the wrong network may not receive the asset as intended.
- Destination: Compare the replacement address from the wallet’s receive screen with the address pasted into the sending interface. For valuable transfers, make a small test first.
- Asset identity: Record the collection contract, token ID, and current owner shown by a reliable explorer or marketplace record.
- Transaction type: Check whether the action is a direct transfer, approval, listing, purchase, or contract interaction. A prompt that says “mint,” “claim,” or “accept” may contain more than a simple transfer.
- Fees: Keep enough native currency for gas fees, but do not fund an exposed wallet more than necessary. Review the gas network and estimated fee before signing.
- Listings and integrations: Cancel or review active listings, marketplace permissions, automated trading tools, and connected applications. Moving an NFT may not remove a separate listing or permission.
- Identity links: If the old wallet controls an ENS name, social profile, creator payout address, or public collection identity, decide separately how to update it. Do not expose the new vault address unnecessarily; see ENS and NFT Wallet Identity.
For a deeper same-chain transfer sequence, use How to Move NFTs to a New Wallet Safely. If transaction details are unclear, review the NFT Wallet Transaction Simulation checklist before signing. Gas planning by network is covered in NFT Transfer Gas Planning.
Common mistakes
- Importing the old phrase into a new app: A different interface does not create a different wallet. Generate a new phrase instead.
- Relying on a disconnect button: Website disconnection may end a session but does not necessarily revoke an on-chain approval.
- Clicking search-engine support ads or direct messages: Find support through the official wallet, marketplace, or collection website, not through an unsolicited message.
- Moving everything in one rushed transaction: A wrong chain, wrong address, or malicious contract call can compound the loss. Inventory first and test where appropriate.
- Leaving the old wallet connected for convenience: Use the compromised address only for monitoring and evidence. Create a clean operating wallet for trading, collecting, and payments.
- Assuming a hardware wallet solves every problem: It can improve key isolation when used correctly, but it cannot make a leaked recovery phrase secret again.
- Failing to document creator and payment records: Collectors and creators should preserve receipts, royalties, sales, fees, refunds, and transfer hashes. The NFT Payment Reconciliation Workflow can help organize this evidence.
When to revisit
Revisit this checklist immediately after any suspected phishing event, before migrating valuable NFTs, and during a periodic wallet-security drill. A practical review can be brief: verify that recovery phrases are offline, remove unused applications, inspect approvals and active sessions, confirm backup access, and check that each wallet still has a clear purpose.
Review the workflow before seasonal collecting or creator-payment cycles, when you add a marketplace or wallet integration, and whenever a wallet, chain explorer, approval tool, or marketplace changes its transaction screens or reporting process. Interfaces and procedures can change, so confirm network support and official contact routes at the time of use rather than relying on an old bookmark or message.
Finally, keep a current asset inventory with wallet labels, chain, contract, token ID, intended custodian, and last review date. Separate a public-facing wallet from a high-value vault and a payment wallet where possible. Clear roles make a future incident easier to contain—and reduce the chance that a rushed recovery decision creates another compromise.