A message about a locked wallet or failed transaction can create pressure to act before checking who sent it. The request may arrive by email, direct message, a search advertisement, or a reply to a public complaint. A useful response begins by separating the claim in the message from information you can verify through a channel you already trust.
Stop the conversation before opening its route to support
Do not use the message's link, telephone number, or attachment to establish whether the message is genuine. Open the service through a known application or an address you have independently verified. If you cannot identify the correct service, pause rather than accepting help from the first account that offers it.
The FTC's phishing guidance explains common ways messages try to obtain sensitive information. In a wallet conversation, urgency and familiar branding are reasons to check carefully, not proof that the sender has access to an official support system.
Identify exactly what is being requested
Read the request as an action: disclose a secret, install software, connect an account, sign something, transfer funds, or give another person control of the device. Do not let labels such as "verification" or "synchronization" replace that description.
Treat recovery phrases, private keys, account passwords, and access codes as sensitive credentials. Follow the wallet provider's official security instructions and do not disclose them in response to an unsolicited contact. If you do not understand what a signing request authorizes, stop and seek clarification through a trusted channel before approving it.
Keep troubleshooting away from public secrets
An error can often be described without posting sensitive information. Check screenshots for balances, account details, addresses, identifiers, and visible notifications before sharing them. Use only the information the verified support process requires, and follow its instructions for submitting it securely.
Do not install remote-access tools or unknown browser extensions just because someone claims they will fix the problem quickly. CISA's phishing resources provide another starting point for recognizing suspicious requests and reporting them through appropriate channels.
Be cautious about a second offer to recover a loss
If money or credentials may already have been exposed, keep a factual record of the event and contact the relevant provider through its official process. A new account promising guaranteed recovery can create further pressure at an already difficult moment. Do not pay an unsolicited recovery fee or provide more credentials because a stranger says the first loss can be reversed.
Record the messages, relevant account information, and transaction references through a secure method. Follow appropriate reporting routes for your situation. Preserve evidence without continuing an unsafe conversation simply to obtain more screenshots.
Prepare before the next urgent message
Save the provider's official support route, learn its security recommendations, and know how to report a suspicious contact. Review the security of the accounts and devices you actually use rather than adding unverified tools in response to a scare.
The decision does not need to happen at the speed a stranger demands. A legitimate technical question can be approached through an independently established channel. When a message makes access to your secrets the condition for receiving help, that request deserves a firm pause and a separate verification process.
Related reading: Artificial Intelligence and Cryptocurrency: Where the Two Really Meet