Why you should know this
This security concept can affect access, identity, funds or recovery. Understanding it before funding helps us pause and verify instead of depending on memory during stress.
The short answer

This lesson covers official download sources, publisher checks, clones and dangerous permission requests.
Common crypto impersonation patterns
| Claimed role | Typical request | Safer verification |
|---|---|---|
| Provider support | OTP, password, seed phrase or remote access | Open the official app and create a case there |
| Project team | Connect wallet for migration or airdrop | Check independently published project channels and contract details |
| Government or police | Immediate crypto payment to avoid arrest | Contact the agency through its official public number |
| Employer or recruiter | Pay equipment, training or release fee in crypto | Verify the employer and written hiring process independently |
| Friend or family | Urgent transfer to a new wallet | Call a known number and confirm the request |
| Recovery expert | Upfront fee or wallet secret to recover losses | Treat guaranteed recovery as a red flag and use official reporting routes |
The PAUSE check
P — Pause the requested action. Do not click, install, sign or send while the message controls the clock.
A — Ask what authority is being requested. Is it a public address, secret, login, remote access, wallet signature or payment?
U — Use an independent route. Open the bookmarked app or type the known domain. Contact the person or provider through a number already on record.
S — Study the full destination. Check the entire domain, app publisher, wallet address, asset, network and transaction preview.
E — Escalate and preserve evidence. Report through official channels and retain the message, URL, account, time and transaction ID without forwarding dangerous links casually.
Try PAUSE as a two-minute drill. Imagine a message says a ₱25,000 withdrawal is pending and asks for an OTP. Pause the reply; name the requested authority; open the provider from your bookmark; inspect account activity; report the message. The same routine works even if the grammar, logo and caller ID look perfect.
A familiar Philippine or Asian example
Lia, a Filipino mobile user, opens this lesson before adding funds. She writes three things: the official channel, the action or secret that authorizes access, and the recovery or escalation path. She keeps passwords, recovery phrases and identity documents out of the exercise.
One risk or limitation
An app-store listing reduces some risk but does not replace verification. Compare the publisher, official website link, permissions, update history and spelling. Avoid installation files sent through chat. A fake wallet may work normally until a seed phrase is entered.
For browser wallets, bookmark the official site. Review extension permissions and remove duplicate or unknown wallet extensions.
How this connects to market mastery
Market mastery includes operational survival. Good analysis cannot help if an account, device, recovery method or transfer process fails before the market decision is completed.
Quick check — no money needed

Without opening a real account or sending funds, write a three-step plan for the situation in this lesson. Mark which step must use an independently found official channel.
If you can explain your answer and name the main limitation, this lesson is complete.
This lesson explains fake support, authority pressure and secret requests using safe recognition patterns.
*Cryptocurrency and virtual asset transactions are highly volatile and irreversible, may result in significant losses, and do not guarantee returns; customers should trade only after understanding the risks involved.