Look-alike recipient address: contain the damage and report it
Stop copying addresses from transaction history. Compare the entire intended address with the actual recipient and preserve the suspicious history entry before reporting the loss.
What to do now
- Save the misleading history entry, actual outgoing transaction and intended address source. Distinguish a misleading incoming transfer from your own outgoing payment.
- Use a clean, trusted device if clipboard replacement is suspected. Review saved recipients and active sessions through official account controls; do not delete evidence while securing access.
- Report the hash and recipient to the sending venue through the app. If theft is suspected, retain a case reference for the appropriate authorities rather than negotiating with unsolicited recovery agents.
What may be possible
If a platform controls the recipient, it may assess a report under its procedures. If an attacker controls the keys, a screenshot cannot authorize a reversal. Treat requests for an advance rescue payment as a warning sign.
Venues may apply different recovery conditions. Check the official recovery page if support directs you there; ask about eligibility and any terms before authorizing action. No outcome or completion date is promised.
Choose the official contact
For each platform below, contact official support from inside its app. These links are context, not a claim that a particular recovery service is available.
- Bitget · security guidance
- OKX · security guidance
- Binance · security guidance
- Bybit · security guidance
- Gate · security guidance
Avoid recovery scams
No legitimate support agent asks you to send your seed phrase, private key or authentication code. Never disclose a 2FA code to a person; enter it only in an official flow you initiated. Reject unsolicited direct messages, remote-control requests and wallet connections offered as recovery shortcuts.