Wallet security warning during a swap: what to verify before proceeding

A wallet security warning is a reason to stop and identify the flagged risk. It is not proof of every possible threat, but dismissing it without understanding the request removes information that may prevent loss.

Read what triggered the warning

Does it concern the website domain, token, recipient, spender, approval size or predicted asset changes? MetaMask’s security-alert guidance distinguishes checks and alerts around sites, addresses, tokens and signing requests.

Save the warning text without exposing secrets. Compare the flagged address or contract with independently verified official documentation.

Look for a concrete explanation

A recently deployed contract may lack history; a malicious request may have strong adverse signals. Those situations should not be collapsed into one generic “scanner error.” If the application claims a false positive, verify that claim through its genuine support and the security provider’s documented reporting process.

Do not switch to another wallet simply to avoid seeing the same warning. A different interface may have different coverage while the underlying request stays harmful.

Absence of a warning is not approval

Scanners can miss new or unsupported behavior. You still need to verify token identity, spender, amount and recipient. A clean simulation also answers a narrower question than whether the trade is wise or the contract trustworthy.

If you cannot resolve a material discrepancy, decline the request. A missed trade is a reversible decision; a signed transfer or broad permission can have consequences that a later explanation cannot undo.