Impersonation domains and search ads
Impersonation domains and search ads is easier to manage when the interface label is separated from the actual on-chain object. In the context of Phishing & Scams, review the network, address, contract, request type and expected result rather than relying on a token name, icon or a single status line. Similar-looking addresses and asset symbols can exist on different networks while their states remain independent.
A practical way to work with Impersonation domains and search ads is to break the action into source, destination, permissions or amount, network state and final outcome. When phishing is involved, keep information that can be checked independently, such as a transaction hash, contract address, block status or the selected network. This makes it easier to distinguish a delayed interface from the real on-chain result.
Security remains part of Impersonation domains and search ads. A legitimate wallet flow does not require you to send a seed phrase, private key or verification code to another person or type those credentials into an unfamiliar website. Treat wallet connection, message signing, transaction signing and token approvals as separate requests, and stop when the domain, contract, allowance or result does not match what you intended.
- Confirm the network, address or contract involved in Impersonation domains and search ads
- Keep verifiable public information when phishing is involved
- Never send a seed phrase, private key or verification code to anyone
Fake support and fake airdrops
Fake support and fake airdrops is easier to manage when the interface label is separated from the actual on-chain object. In the context of Phishing & Scams, review the network, address, contract, request type and expected result rather than relying on a token name, icon or a single status line. Similar-looking addresses and asset symbols can exist on different networks while their states remain independent.
A practical way to work with Fake support and fake airdrops is to break the action into source, destination, permissions or amount, network state and final outcome. When domain is involved, keep information that can be checked independently, such as a transaction hash, contract address, block status or the selected network. This makes it easier to distinguish a delayed interface from the real on-chain result.
Security remains part of Fake support and fake airdrops. A legitimate wallet flow does not require you to send a seed phrase, private key or verification code to another person or type those credentials into an unfamiliar website. Treat wallet connection, message signing, transaction signing and token approvals as separate requests, and stop when the domain, contract, allowance or result does not match what you intended.
- Confirm the network, address or contract involved in Fake support and fake airdrops
- Keep verifiable public information when domain is involved
- Never send a seed phrase, private key or verification code to anyone
Never submit sensitive credentials
Never submit sensitive credentials is easier to manage when the interface label is separated from the actual on-chain object. In the context of Phishing & Scams, review the network, address, contract, request type and expected result rather than relying on a token name, icon or a single status line. Similar-looking addresses and asset symbols can exist on different networks while their states remain independent.
A practical way to work with Never submit sensitive credentials is to break the action into source, destination, permissions or amount, network state and final outcome. When support is involved, keep information that can be checked independently, such as a transaction hash, contract address, block status or the selected network. This makes it easier to distinguish a delayed interface from the real on-chain result.
Security remains part of Never submit sensitive credentials. A legitimate wallet flow does not require you to send a seed phrase, private key or verification code to another person or type those credentials into an unfamiliar website. Treat wallet connection, message signing, transaction signing and token approvals as separate requests, and stop when the domain, contract, allowance or result does not match what you intended.
- Confirm the network, address or contract involved in Never submit sensitive credentials
- Keep verifiable public information when support is involved
- Never send a seed phrase, private key or verification code to anyone
Remote-control and screen-sharing risk
Remote-control and screen-sharing risk is easier to manage when the interface label is separated from the actual on-chain object. In the context of Phishing & Scams, review the network, address, contract, request type and expected result rather than relying on a token name, icon or a single status line. Similar-looking addresses and asset symbols can exist on different networks while their states remain independent.
A practical way to work with Remote-control and screen-sharing risk is to break the action into source, destination, permissions or amount, network state and final outcome. When airdrop is involved, keep information that can be checked independently, such as a transaction hash, contract address, block status or the selected network. This makes it easier to distinguish a delayed interface from the real on-chain result.
Security remains part of Remote-control and screen-sharing risk. A legitimate wallet flow does not require you to send a seed phrase, private key or verification code to another person or type those credentials into an unfamiliar website. Treat wallet connection, message signing, transaction signing and token approvals as separate requests, and stop when the domain, contract, allowance or result does not match what you intended.
- Confirm the network, address or contract involved in Remote-control and screen-sharing risk
- Keep verifiable public information when airdrop is involved
- Never send a seed phrase, private key or verification code to anyone
A verification order for suspicious requests
A verification order for suspicious requests is easier to manage when the interface label is separated from the actual on-chain object. In the context of Phishing & Scams, review the network, address, contract, request type and expected result rather than relying on a token name, icon or a single status line. Similar-looking addresses and asset symbols can exist on different networks while their states remain independent.
A practical way to work with A verification order for suspicious requests is to break the action into source, destination, permissions or amount, network state and final outcome. When remote control is involved, keep information that can be checked independently, such as a transaction hash, contract address, block status or the selected network. This makes it easier to distinguish a delayed interface from the real on-chain result.
Security remains part of A verification order for suspicious requests. A legitimate wallet flow does not require you to send a seed phrase, private key or verification code to another person or type those credentials into an unfamiliar website. Treat wallet connection, message signing, transaction signing and token approvals as separate requests, and stop when the domain, contract, allowance or result does not match what you intended.
- Confirm the network, address or contract involved in A verification order for suspicious requests
- Keep verifiable public information when remote control is involved
- Never send a seed phrase, private key or verification code to anyone