Pasted recipient changed: how to stop a misdirected swap

If the pasted address differs from the intended recipient, reject the transaction. Repeatedly copying and trying again is not enough; the source page, clipboard or device environment may be compromised or simply wrong.

Compare at two points

First verify the source address from a trusted receive view or authenticated service page. Then compare the complete address in the wallet’s actual signing request. Use a hardware device’s trusted display where supported.

Ethereum’s security guidance recommends careful transaction and address checks. Clear-signing support can make relevant destination information reviewable, but only for supported transaction formats.

Do not trust a partial match

Checking only the first and last characters can miss a deliberate lookalike. A prior successful test transfer also does not prove the address in a new request is unchanged.

For swaps, a correct top-level router address does not necessarily validate the final output recipient. Review the operation’s recipient field or supported decoded summary.

Resolve the environment before retrying

Investigate unexpected browser extensions, downloads and device behavior using trusted tools. Obtain the recipient through another trusted channel or clean device if necessary. Do not enter a seed on a diagnostic site offered by a stranger.

If a wrong-recipient transaction already confirmed, preserve the hash and exact source and destination addresses. Changing the clipboard afterward cannot reverse it. If it remains pending, a supported cancellation may be attempted, but success must be confirmed onchain.