Crypto scams often combine urgency, impersonation and irreversible payment. Stop the conversation, find the service through an independent official channel, never share a recovery phrase and reject guaranteed-return claims.

Legitimate support never needs your recovery phrase.

Verify a request independently.

Domain, identity, network, address, amount and permissions.
Common scenarios
Fake support offers to validate a wallet. A false opportunity promises returns or rewards. Phishing copies a website and requests a connection or signature. Recovery scammers target victims again.
- Fake support
- Guaranteed investment
- Invented airdrop
- Copied site or app
- Recovery scam
Verify before acting
Do not follow the received link. Open a bookmark or type the official domain. Check identity, destination, network and the exact powers granted by a signature. Reject unlimited or unclear approvals.
- Create a deliberate pause
- Compare the full domain
- Check official announcements
- Limit amount and permissions
If a secret was exposed
Stop contact and sign nothing else. From a clean device, change compromised access. If the phrase was revealed, create a new wallet and move remaining assets. Review and revoke affected approvals.
Preserve evidence and report
Save URLs, transaction identifiers, times, profiles and screenshots without exposing secrets. Contact the provider and your competent authority. Reject anyone guaranteeing recovery.
Check an unexpected request
A private message with an official logo proves neither the sender’s identity nor an urgent problem. Find the service using its known address and contact support through that channel instead of following the link supplied by the sender.
- Never disclose a recovery phrase, private key or verification code.
- Keep the URL, message and time if you need to report the attempt.
Practical case: decision and limits
A message promises a refund but first requests a signature or an “unlocking” payment. Stop and reach the service through a previously verified address. Preserve the message, domain and signing request without publishing secrets. Brand impersonation, logos and testimonials prove nothing. A supposed fund recovery service may be a second scam.
A concrete verification
Find the request inside your account opened from a verified bookmark. Logos do not establish origin.
Hypothetical case: a small withdrawal does not validate a platform
An interface shows €1,800 profit and allows a first €20 withdrawal. A contact then demands a €300 “tax” to a private address to release the remainder. The small withdrawal proves neither the displayed gains nor the entity’s reliability. Compare each payment recipient with independently checked terms and identity. Do not treat the displayed balance as evidence of available funds. For the fictional case, build a timeline of money actually sent and received using payment references, separately from the interface’s claimed balance. A change on that display is not a verified incoming payment. Do not publish secrets or third-party data when seeking help; use independently located official channels.
- Keep URLs, messages, payment references and chronology; screenshots need their context.
- Check contact details through an official channel found independently of the conversation.
- A new contact promising recovery for an advance payment may extend the same fraud.
Hide the token in the wallet
Changes the displayed token list; changes neither the on-chain balance nor permissions.
- Ends the interface connection; a permission already recorded on-chain may remain active.
- Protects local access depending on the software; does not replace the private key or revoke permissions.
Protect accounts from fake sign-in screens
Where supported, use a passkey or FIDO security key for both your platform account and its recovery email. This authentication is bound to the site where it was set up. An SMS or one-time code can be entered on a fake sign-in page. Open the service from a bookmark or its official app and review the available account recovery methods as well. A self-custody wallet’s recovery phrase remains a separate secret.
Signal, risk and response
| Signal | Risk | Safe response |
|---|---|---|
| Urgency or secrecy | Prevent verification | Pause and contact the official channel |
| Recovery phrase request | Complete takeover | Share nothing and leave |
| Guaranteed return | False opportunity | Reject and verify the entity |
| Unlimited approval | Future token spending | Reject or limit precisely |
Frequently asked questions
Can support ask for a screenshot?
Redact data and never send a phrase, key, backup QR or 2FA code.
Is disconnecting the wallet enough?
No. On-chain approvals may remain active until revoked.
Can a fraudulent transaction be reversed?
Usually not after confirmation. Notify providers and authorities and avoid recovery scammers.
Verifiable sources
FTC: Cryptocurrency scams
CISA: Recognize and report phishing
Ethereum.org: Security and scam prevention- W3C: WebAuthn public-key authentication
CISA: Phishing-resistant authentication
Independent educational content reviewed against primary documentation. No personalized recommendation or promise of returns. Updated November 15, 2026
Prepare and continue reading

Useful background
- How to choose a crypto wallet
A crypto wallet manages the keys that authorize operations; it does not physically hold the assets. The right choice depends on use, value at risk and your ability to protect a recovery phrase without sharing it.
- Message signatures: login, permits and permissions
No immediate paid transaction does not mean no risk. Inspect request type, domain, network, contract, spender, value and expiry. Reject requests whose scope your wallet cannot explain.

Continue to the next step
- What to do after a crypto security incident
Stop signing. Use a trusted device and a new recovery phrase if exposed. A sweeper bot can steal gas top-ups: consult official wallet support before attempting transfers.
- Token approvals: review and revoke spending permissions
On each network, inspect approved spenders, token and limit. Revoke permissions you no longer need with a trusted tool, then verify the confirmed transaction. If a recovery phrase is exposed, revocation alone is insufficient.




