Authenticate the domain
Use a saved verified route, inspect redirects and compare legal, privacy and contact identities.
This page is a decision worksheet built around a specific search task. It separates observable records, first-party wording and unresolved claims so the conclusion can be checked again after a material change.
Verify wallet prompts
Read the network, destination and message being signed. A login signature should not authorise asset transfer or unlimited token access.
Protect authentication
Never disclose passwords, one-time codes, seed phrases, private keys or recovery codes to support.
Reject remote access
Do not install screen-control, accessibility or wallet software from chat messages to solve a payment problem.
Prepare incident steps
Secure email and wallet sessions, revoke risky approvals and preserve hashes, hostnames and timestamps before escalating.
Recovery guarantees are a second risk event
Anyone promising certain recovery in exchange for an upfront crypto payment, wallet connection or seed phrase should be treated as unverified.
Questions this page resolves
Is a wallet-connect prompt safe?
Only after verifying the domain and reading the exact permissions or message.
Can support ask for a seed phrase?
No legitimate troubleshooting needs secret recovery material.
What is the first step after a suspicious signature?
Disconnect, review approvals, secure accounts and seek verified wallet guidance.