Seed phrases and private keys remain under user control. Review signing, approval and transaction requests independently.
Common phishing entry points
The same interface action can have different consequences across networks and contracts, so context always matters. In the context of “Common phishing entry points,” pay particular attention to phishing site, fake support, and fake airdrop. Start by identifying the network or request type, then compare what the wallet shows with what you actually intend to do. For transactions, verify the asset, amount, gas implications, destination and the transaction hash that is produced. This does not add ceremony for its own sake; it moves the most important checks to the point before an irreversible action.
Within Phishing & Scams, interface messages are only one source of information. Network congestion, RPC behavior, smart-contract state and token-contract differences can all affect what you see. Keep something independently verifiable in view, such as the correct network name, destination address, contract address or transaction hash, and do not sign or approve a request that you cannot explain in plain language. Afterward, use a transaction hash, explorer or wallet history to verify the final state instead of relying only on a success message.
Practical checks
- Confirm that common phishing entry points matches the intended network and action
- Keep a verifiable reference and review the outcome after completion
Signs of fake support and fake airdrops
Security is not one setting. It comes from understanding accounts, networks, signatures, approvals and the device environment together. In the context of “Signs of fake support and fake airdrops,” pay particular attention to fake support, fake airdrop, and domain. Start by identifying the network or request type, then compare what the wallet shows with what you actually intend to do. For transactions, verify the asset, amount, gas implications, destination and the transaction hash that is produced. This does not add ceremony for its own sake; it moves the most important checks to the point before an irreversible action.
Within Phishing & Scams, interface messages are only one source of information. Network congestion, RPC behavior, smart-contract state and token-contract differences can all affect what you see. Keep something independently verifiable in view, such as the correct network name, destination address, contract address or transaction hash, and do not sign or approve a request that you cannot explain in plain language. For unfamiliar contracts or larger values, testing a smaller, clearly understood action first can reduce operational mistakes.
Practical checks
- Confirm that signs of fake support and fake airdrops matches the intended network and action
- Keep a verifiable reference and review the outcome after completion
Verify domains and download sources
The safest workflow starts with identifying the network and the request before any confirmation button is pressed. In the context of “Verify domains and download sources,” pay particular attention to fake airdrop, domain, and clipboard. Start by identifying the network or request type, then compare what the wallet shows with what you actually intend to do. For transactions, verify the asset, amount, gas implications, destination and the transaction hash that is produced. This does not add ceremony for its own sake; it moves the most important checks to the point before an irreversible action.
Within Phishing & Scams, interface messages are only one source of information. Network congestion, RPC behavior, smart-contract state and token-contract differences can all affect what you see. Keep something independently verifiable in view, such as the correct network name, destination address, contract address or transaction hash, and do not sign or approve a request that you cannot explain in plain language. If information conflicts, verify the network, address, contract and transaction hash before deciding what to do next.
Practical checks
- Confirm that verify domains and download sources matches the intended network and action
- Keep a verifiable reference and review the outcome after completion
Clipboard and remote-control risks
When a request is unfamiliar, understanding it before proceeding is more important than completing it quickly. In the context of “Clipboard and remote-control risks,” pay particular attention to domain, clipboard, and remote control. Start by identifying the network or request type, then compare what the wallet shows with what you actually intend to do. For transactions, verify the asset, amount, gas implications, destination and the transaction hash that is produced. This does not add ceremony for its own sake; it moves the most important checks to the point before an irreversible action.
Within Phishing & Scams, interface messages are only one source of information. Network congestion, RPC behavior, smart-contract state and token-contract differences can all affect what you see. Keep something independently verifiable in view, such as the correct network name, destination address, contract address or transaction hash, and do not sign or approve a request that you cannot explain in plain language. For a third-party DApp or smart contract, the wallet can display a request but cannot guarantee the contract logic or the economic result.
Practical checks
- Confirm that clipboard and remote-control risks matches the intended network and action
- Keep a verifiable reference and review the outcome after completion
What to do first when something seems wrong
Security is not one setting. It comes from understanding accounts, networks, signatures, approvals and the device environment together. In the context of “What to do first when something seems wrong,” pay particular attention to clipboard, remote control, and phishing site. Start by identifying the network or request type, then compare what the wallet shows with what you actually intend to do. For transactions, verify the asset, amount, gas implications, destination and the transaction hash that is produced. This does not add ceremony for its own sake; it moves the most important checks to the point before an irreversible action.
Within Phishing & Scams, interface messages are only one source of information. Network congestion, RPC behavior, smart-contract state and token-contract differences can all affect what you see. Keep something independently verifiable in view, such as the correct network name, destination address, contract address or transaction hash, and do not sign or approve a request that you cannot explain in plain language. If information conflicts, verify the network, address, contract and transaction hash before deciding what to do next.
Practical checks
- Confirm that what to do first when something seems wrong matches the intended network and action
- Keep a verifiable reference and review the outcome after completion
Ongoing verification matters more than one-time confidence
When using features related to Phishing & Scams, keep seed phrases and private keys under your own control. imtoken personnel should never ask for those secrets or verification codes. Verify the address, network and amount before a transfer, and review the requesting party and permission scope before signing or approving. On-chain transactions are generally not reversible by a wallet alone, and third-party DApps or contracts can introduce separate risks.