On this pageCore principlesCommon risk scenariosHow to identify problemsWhat to do nextSecurity checklist
Core security checks
  • Keep seed phrase backups offline
  • Never send private keys or verification codes
  • Verify domains, networks and addresses
  • Review every signature and approval
  • Review and revoke approvals you no longer need

Core principles

Phishing & Scams makes more sense when fake websites, fake support, fake airdrops, clipboard risk, urgency pressure are considered as parts of one on-chain workflow. A wallet interface is only the entry point; the important checks concern the network, address, contract and on-chain state.

During real use, confirm the active network and account first, then verify the object, scope and expected outcome related to fake websites. Any action that changes assets, permissions or account state deserves a full review before confirmation.

Common risk scenarios

During real use, confirm the active network and account first, then verify the object, scope and expected outcome related to fake websites. Any action that changes assets, permissions or account state deserves a full review before confirmation.

For fake support, prefer information that can be independently checked: the wallet transaction summary, the relevant network explorer, an explicit contract address or an official product page. When a request is unclear, stop before signing or transferring and verify the network and on-chain record from a trusted path.

How to identify problems

For fake support, prefer information that can be independently checked: the wallet transaction summary, the relevant network explorer, an explicit contract address or an official product page. When a request is unclear, stop before signing or transferring and verify the network and on-chain record from a trusted path.

When fake airdrops is involved, separate display data from on-chain facts. Names, icons and fiat estimates may come from external data sources, while balances, transaction state and approvals should be verified on the selected network.

Do not continue with any request that asks for a seed phrase, private key or verification code. Official personnel will not ask for these secrets.

What to do next

When fake airdrops is involved, separate display data from on-chain facts. Names, icons and fiat estimates may come from external data sources, while balances, transaction state and approvals should be verified on the selected network.

For clipboard risk, retain the transaction hash or other useful reference when appropriate. On-chain transactions generally cannot be reversed unilaterally by a wallet, which makes pre-broadcast checks of the address, network, amount and permissions especially important.

Security checklist

For clipboard risk, retain the transaction hash or other useful reference when appropriate. On-chain transactions generally cannot be reversed unilaterally by a wallet, which makes pre-broadcast checks of the address, network, amount and permissions especially important.

Finally, consider urgency pressure. Third-party DApps, smart contracts and network services can introduce technical, operational and market risk. Unclear signatures, unnecessarily broad approvals, or any page asking for a seed phrase or private key are reasons to stop and re-check the request.