The short answer: before acting on an unexpected message that claims to be from a crypto platform or its support team, treat the message as unverified and check its story and its ask against the provider's own stated contact policy — found only through channels you navigate to yourself. The message itself is evidence to scrutinize, not a routing instruction. Note that the general phishing indicators below come from a consumer-protection source that describes phishing broadly, not from any specific crypto platform's published policy.
Start from the provider, not the message
The safest starting point is the provider's official page for contact and security, reached by typing the address in yourself or opening the official app, not by following a link in the message. Read what that page says about how the provider contacts customers: which channels it uses, what types of requests it makes, and whether it ever asks for passwords or account details by message. That stated policy becomes your reference point.
This matters because scammers routinely impersonate companies people already trust. Source material notes that you might get an unexpected email or text message that looks like it's from a company you know or trust, like a bank or a credit card or utility company, or from an online payment website or app (c07, c08). The familiar name is a lure, not a guarantee.
The goal of the comparison is not to prove a message is fraud. It is to establish whether you have any independent reason to trust it. A message that contradicts the provider's stated contact policy has no such reason, and a message that happens to match some details still has not earned trust on its own.
Read the message's story
Phishing messages often tell a story designed to make clicking or replying feel urgent or routine. The message could be from a scammer who says they've noticed some suspicious activity or log-in attempts — they haven't; claims there's a problem with your account or your payment information — there isn't; or says you need to confirm some personal or financial information — you don't (c10, c11, c12). Other common storylines include an invoice you don't recognize (it's fake), a link to make a payment (which may carry malware), or an invitation to register for a government refund (c13, c14, c15).
Each of these storylines makes a specific ask, and the ask is what you compare. Does the provider's policy say it would raise an account problem by message, or would it direct you to log in through its own app or site? Does the policy say it ever requests passwords, account numbers, or identity details by email or text? These general phishing patterns are widely reported precisely because the mismatch is detectable, even when the message looks convincing: at first glance, an email can look real but isn't, and scammers are hoping you won't notice it's a fake (c16, c17, c18).
The stakes are real because phishing messages are used to try to steal your passwords, account numbers, or Social Security numbers (c01). If they get that information, they could get access to your email, bank, or other accounts, or sell your information to other scammers (c02, c03). Scammers launch thousands of phishing attacks like these every day — and they're often successful (c04).
A screening method, kept explicitly general
The framework below is my own general procedure for the comparison. It is not attributed to the consumer-protection source, which does not describe any provider's contact-policy structure. Use it as a way to organize your check, not as an established standard.
- Channel: How does the provider's official page say it contacts you — email, in-app notification, phone, or other?
- Ask: Does the message request a password, account number, identity detail, or payment, and does the policy describe such a request?
- Action path: Does the policy send you to a URL in a message, or does it instruct you to log in through the app or site on your own?
- Reply expectation: Does the provider say it expects a reply to a text, or does it route everything through support reached inside your account?
To check a message against the policy, use only the official channel you navigated to. Don't test the message's link, download an attachment, or reply to compare behavior — the act of comparing can itself expose you.
Worked example: a hypothetical policy check
The following is a hypothetical illustration with invented values. It is not evidence about any real provider, and any policy values shown are made up for the example.
| Element | Hypothetical official policy | Example message |
|---|---|---|
| Channel | In-app notifications only | Unexpected email asking to reset a password |
| Ask | Never asks for passwords or account numbers by message | Requests password confirmation via a link |
| Action path | Log in through the official app or site | Directs to a URL supplied in the email |
In this hypothetical, each row conflicts with the invented policy. One clear conflict is enough to treat the message as unverified and to act only through the official channel you navigated to yourself. The purpose of the example is to show the comparison's shape, not to supply a verdict about any real message.
What the source does not say
- The source does not describe any specific provider's contact policy, contact channels, or reply expectations. Any such structure above is a general screening method, not established fact.
- The source does not address crypto platforms, wallets, or token identities specifically; its examples are banks, credit card or utility companies, and online payment websites or apps (c07, c08).
- The source does not state how to verify a specific domain or sender, and it does not provide a test to confirm that a particular message is fraudulent.
- The source does not say how to recover funds or credentials once they have been lost, and nothing here should be read as a recovery promise.
The useful conclusion is narrow: an unexpected message is a claim, and the provider's own published contact policy is the standard you compare it against. Use that standard to decide whether to act, and always act through a channel you opened yourself.