On this page
Common scam entry pointsFake support patternsFake airdrops and claimsRecognizing impersonation sitesResponding to suspicious activityCommon scam entry points
When reviewing Common scam entry points, separate search ads, direct messages, and group chats. They may appear in the same workflow, but they represent different layers of the action. On this Phishing & Scam Awareness page, the goal is to build a verifiable mental model rather than depend on a single interface cue. Before approving anything, identify the network, the object being changed, and whether the request matches the task you intended to perform.
A useful routine is to review items in a fixed order: confirm direct messages, verify group chats, inspect QR codes, and keep short links for later reference. If a page unexpectedly asks for search ads, stop and verify the source instead of continuing simply because the workflow looks familiar.
From a security perspective, Common scam entry points should be considered together with group chats, QR codes, and short links. A legitimate review flow does not require you to reveal a seed phrase, private key, or verification code. Requests involving search ads or direct messages can change permissions or asset state, so review them individually and reject anything you do not understand.
Fake support patterns
In practice, unsolicited contact often tells you whether you are in the right context, requesting seed phrases affects the resulting state, and remote control helps with independent verification afterward. Do not rely only on a success message in the interface. Where on-chain state is involved, compare it with pressuring transfers and fake tickets so you can distinguish presentation from the actual network result.
Fake support patterns also has failure modes. Congestion, incorrect parameters, insufficient balances, contract conditions, or third-party service changes can produce unexpected results. Start with the objective state of requesting seed phrases, remote control, and pressuring transfers before retrying. Repeated submissions without understanding the cause can add fees or duplicate actions.
When reviewing Fake support patterns, separate remote control, pressuring transfers, and fake tickets. They may appear in the same workflow, but they represent different layers of the action. On this Phishing & Scam Awareness page, the goal is to build a verifiable mental model rather than depend on a single interface cue. Before approving anything, identify the network, the object being changed, and whether the request matches the task you intended to perform.
- unsolicited contact
- requesting seed phrases
- remote control
- pressuring transfers
- fake tickets
Fake airdrops and claims
A useful routine is to review items in a fixed order: confirm unknown token, verify signing, inspect approval, and keep contract for later reference. If a page unexpectedly asks for countdown pressure, stop and verify the source instead of continuing simply because the workflow looks familiar.
From a security perspective, Fake airdrops and claims should be considered together with signing, approval, and contract. A legitimate review flow does not require you to reveal a seed phrase, private key, or verification code. Requests involving countdown pressure or unknown token can change permissions or asset state, so review them individually and reject anything you do not understand.
In practice, approval often tells you whether you are in the right context, contract affects the resulting state, and countdown pressure helps with independent verification afterward. Do not rely only on a success message in the interface. Where on-chain state is involved, compare it with unknown token and signing so you can distinguish presentation from the actual network result.
Recognizing impersonation sites
Recognizing impersonation sites also has failure modes. Congestion, incorrect parameters, insufficient balances, contract conditions, or third-party service changes can produce unexpected results. Start with the objective state of domain name, spelling, and certificate before retrying. Repeated submissions without understanding the cause can add fees or duplicate actions.
When reviewing Recognizing impersonation sites, separate spelling, certificate, and copied pages. They may appear in the same workflow, but they represent different layers of the action. On this Phishing & Scam Awareness page, the goal is to build a verifiable mental model rather than depend on a single interface cue. Before approving anything, identify the network, the object being changed, and whether the request matches the task you intended to perform.
A useful routine is to review items in a fixed order: confirm certificate, verify copied pages, inspect download entry, and keep domain name for later reference. If a page unexpectedly asks for spelling, stop and verify the source instead of continuing simply because the workflow looks familiar.
Responding to suspicious activity
From a security perspective, Responding to suspicious activity should be considered together with 停止操作, disconnecting, and revoking approvals. A legitimate review flow does not require you to reveal a seed phrase, private key, or verification code. Requests involving move to a new wallet or preserve evidence can change permissions or asset state, so review them individually and reject anything you do not understand.
In practice, disconnecting often tells you whether you are in the right context, revoking approvals affects the resulting state, and move to a new wallet helps with independent verification afterward. Do not rely only on a success message in the interface. Where on-chain state is involved, compare it with preserve evidence and 停止操作 so you can distinguish presentation from the actual network result.
Responding to suspicious activity also has failure modes. Congestion, incorrect parameters, insufficient balances, contract conditions, or third-party service changes can produce unexpected results. Start with the objective state of revoking approvals, move to a new wallet, and preserve evidence before retrying. Repeated submissions without understanding the cause can add fees or duplicate actions.