Start with the request, not the branding
A familiar logo, search placement or convincing reply does not establish who controls a message. Read what the sender wants you to do: transfer assets, disclose a secret, install software or approve a wallet request. Urgency can make that request harder to evaluate.
The FTC describes schemes that impersonate trusted businesses or authorities and direct people to pay in cryptocurrency. A claim that a transfer is needed to “protect” funds is a reason to stop and verify independently, not evidence of an emergency that the sender can solve.
Evidence: FTC: cryptocurrency scams
Treat secret credentials as a boundary
A seed phrase, private key or account password is not a support ticket attachment. Ethereum’s security guidance warns about imitation sites and unofficial support channels seeking credentials. Do not enter recovery material into a page reached through an unsolicited message.
Verification means leaving the message and using a previously trusted app, bookmark or independently checked official domain. Replying to the same sender or calling the number in the warning does not establish a separate source. CryptoTrades does not need wallet credentials to explain a calculator.
Evidence: Ethereum security and scam prevention
A wallet permission can outlast a browser session
A connection prompt, token allowance and transaction approval describe different actions. Understand the permission being requested rather than assuming that a familiar-looking wallet dialog makes the website trustworthy.
Ethereum’s token-access guide explains that disconnecting a wallet from a site does not itself remove previously granted spending allowances. That distinction is not a claim that revocation resolves every kind of compromise: disclosed keys and malicious permissions are different problems.
Evidence: Ethereum: token access and revocation
Walk through a fictional support message
Imagine an unexpected message saying “your holdings will be frozen; validate your wallet now.” The example is invented and links to no website. The warning sign is the requested action combined with unsolicited urgency, not a particular company name.
An independent check should ask who controls the contact channel, whether a genuine account notice exists and what the requested permission would allow. Avoid opening a “verification” page just to see if it looks professional. A polished screen is not a technical assessment.
| Request | Reason to pause |
|---|---|
| Send funds to a “safe” address | The sender would determine where assets go |
| Paste recovery words into support chat | Secret signing material would be exposed |
| Approve an unexplained allowance | Spending authority may extend beyond the session |
If you suspect an incident, preserve evidence safely
Stop interacting with the suspicious contact. Keep public transaction identifiers, the site address, dates and a redacted description for the genuine provider or relevant reporting channel. Never include recovery words or passwords in an incident report.
Use the wallet or provider’s official incident guidance for the particular compromise. This checklist cannot inspect permissions or recover assets. Be cautious about a second unsolicited offer promising recovery in exchange for payment; Ethereum’s scam-support guidance specifically warns about recovery scams.
Evidence: Ethereum scam help
Keep tracking separate from security verification
The manual portfolio tool records quantities and prices you type. It neither holds keys nor scans allowances, so a normal-looking balance there says nothing about whether a wallet or account is secure.
Use fictional entries when learning the tracker. If you need to report a site-content problem, send the page URL and a source through Contact, without private financial records. Checking warning signs reduces blind spots; it does not certify a site, wallet or transaction.
Evidence: CryptoTrades manual portfolio tracker
Sources & method
- FTC: cryptocurrency scams
Consumer guidance on impersonation and payment demands; not an assessment of any named incident. Checked 2026-10-29.
- Ethereum security and scam prevention
Primary ecosystem guidance on phishing, credentials and support channels. Checked 2026-10-29.
- Ethereum: token access and revocation
Explains why disconnecting does not revoke an allowance. No wallet was connected or permissions changed. Checked 2026-10-29.
- Ethereum scam help
Incident context and recovery-scam warning; no recovery service is endorsed. Checked 2026-10-29.
- CryptoTrades manual portfolio tracker
Manual holdings interface; not a wallet, custody service or security scanner. Checked 2026-10-29.
Continue learning
Found an error? Contact the editorial team with the page and supporting source. Never send private account information.