Resource · Public
Crypto Scam Checks before You Connect or Transfer
Recognize impersonation, excessive token permissions and recovery-fee stories through original scenarios, using no real wallet connections.
Image credit
Fictional scam-prevention exercise; excessive permission is a reason to pause, not a predicted loss amount.
FavAcademy · Original FavAcademy educational illustration; public use authorized
Public summary
A polished website or familiar name does not explain what a wallet request will authorize. Work through fictional support, approval and recovery scenarios, then build a pause-and-verify routine without connecting a wallet or sharing a secret.
Focus on the action being requested
Crypto scams often combine a believable story with a request that changes control: reveal a recovery phrase, sign a transaction, approve spending or transfer assets. The story may mention support, a reward or an urgent security update. Start by identifying the action and its consequences rather than deciding from the sender's apparent confidence or design quality.
This guide is a prevention exercise using fictional messages. It needs no actual wallet connection, transfer or seed phrase. It does not promise that a checklist detects every fraud. Its purpose is to make high-impact requests visible and preserve the option to stop when identity, scope or meaning cannot be independently verified.
Separate a familiar name from a verified channel
Imagine an unsolicited message claiming to be wallet support. It copies a logo and says an account must be “synchronized” through a new website. A familiar name or an existing conversation does not establish that the sender controls the official service. Independently locate the actual support documentation rather than using the message's link to verify itself.
The Ethereum project's security guidance warns about impersonation and unsolicited support approaches. Keep the principle specific: an unexpected request for secrets or signing authority is not made safe by a copied brand. Do not install remote-access software or expose the screen of a sensitive wallet merely because someone appears to understand the problem. A convincing helper can still be an unverified counterparty.
Treat recovery material as authority
A recovery phrase or private key can enable control of associated assets under the wallet's design. Sharing it is not the same as providing a public address to receive a transfer. A legitimate educational explanation does not require those secrets. Never put them in a support chat, learning worksheet, screenshot or an unfamiliar website's recovery form.
For a paper exercise, use the words “secret placeholder” rather than inventing a realistic seed phrase. The objective is to recognize the request, not rehearse typing genuine recovery material into a form. A wallet-specific backup process should come from trusted documentation and a controlled setup. It is not validated by a stranger claiming that an emergency exception makes secrecy unnecessary.
Inspect token spending permissions
Some tokens permit a contract to spend up to an approved allowance. That approval is different from a simple transfer and can remain relevant after the initial interaction. MetaMask's documentation explains that excessive or malicious approvals are a common attack path. Understand the spender, asset, network and allowed amount before authorizing such a request.
In a fictional scenario, a task appears to require 12 tokens, but the request seeks an allowance of 1,000. The allowance is more than 83 times the stated task amount. That mismatch needs explanation; it is not proof that exactly 1,000 tokens will be stolen. The risk depends on actual balances, token behaviour and the spender's authority. Do not turn a permission limit into a forecast loss.
Distinguish connection from authorization
Connecting a wallet can reveal an address or enable an application to request later actions, depending on the interface. Signing a message, approving tokens and sending a transaction have different effects. A request described as “just logging in” may still need careful inspection. Do not assume that the absence of an immediate visible transfer makes every signature harmless.
The illustration places identity, action and scope in three checks before any authorization. Ask whether the displayed request matches the task you intended. If the interface does not provide enough information to explain it, pause rather than treating the lack of detail as reassurance. This guide does not provide a universal safe-signature rule; application and wallet behaviour vary.
Recognize the second-payment story
Another fictional message says lost assets can be recovered after paying a fee to “unlock the blockchain.” A demand for more money does not establish recovery authority. Be especially cautious of people contacting victims after a loss with guarantees, insider access or urgent payment deadlines. Public transaction visibility can make a recovery story sound informed without giving the sender any power to reverse it.
Preserve the message and relevant transaction identifiers if safe, but do not publish private account details or engage through a new unverified recovery portal. Investigate official reporting and support channels independently. Recovery possibilities depend on the incident and involved services; no general promise or guaranteed technical reversal is offered here.
Respond to a suspected compromise carefully
Stop interacting with the suspicious application and determine what was exposed: an account password, a token approval, a signing secret or a transfer. Those are different incidents. Use independently verified official guidance appropriate to the wallet and network, and avoid following a second unsolicited set of emergency instructions. A rushed response can create additional harmful transactions.
Revoking a token approval can limit that permission under the relevant token contract, but it cannot make a disclosed private key secret again. Changing an exchange password addresses a different control. If the consequences are unclear, seek qualified assistance through trustworthy channels without disclosing recovery material. This article supplies a classification exercise, not individualized incident-response instructions or a guarantee that lost funds can be recovered.
Retain a small decision record
For each practice scenario, write who contacted you, which channel was independently verified, what action was requested and what authority it would grant. Keep the result as proceed only after sufficient verification, pause or reject. Do not calculate a credibility score that allows several reassuring details to cancel one request for a secret.
A good final explanation says why the action was not authorized. For the allowance example, the unexplained mismatch is enough to pause even without proving criminal intent. For the support example, a copied logo does not verify the channel. The habit to practice is reading and questioning control changes before consenting, while recognizing that no short checklist eliminates the risks of interacting with unfamiliar crypto services.
Continue learning with Crypto Wallets: Custody, Keys, and Recovery Checks and Compare Crypto Exchanges beyond the Trading Fee.
Risk disclosure
Educational examples are hypothetical. Costs, execution and product terms vary; no outcome or suitability is promised.