Disconnecting a Dapp Does Not Remove Its Token Allowance

Review browser connections and on-chain allowances separately when retiring an application.

Disconnecting a Dapp Does Not Remove Its Token Allowance — editorial illustration
Editorial illustration, not evidence of an incident.

Scope: MetaMask dapp connections

Disconnecting removes a site's connection to the wallet through its permission controls. MetaMask's help documentation explicitly distinguishes this from revoking token approvals. An allowance already recorded on chain can remain usable by the spender after the browser connection is removed.

Review two separate things

First inspect the wallet's connected-site permissions and remove connections you no longer need. Then review relevant token allowances on the correct network using an independently verified approval tool. Confirm the spender and token before signing a revocation, and check that the transaction has actually confirmed. Menu names can change between wallet versions, so use the current official instructions.

Avoid a false all-clear

Public blockchain activity remains public after a site is disconnected. Disconnecting is also not a cure for a stolen recovery phrase or private key. Keep the action you took precise when recording an incident: site disconnected, allowance revoked and secret replaced are different events with different effects. If a suspicious page promises to perform all of them with one unexplained signature, stop. A tidy list of connected sites alone does not establish that the account has no remaining on-chain permissions.

Source and review date

MetaMask Help Center — original source. Original publication date not verified in this review. Source checked: 2026-10-23.

This is an original Wallet Beep editorial summary. Consult the linked source for its full context and any later updates.

RELATED READING

Found an error in the facts or sources? Send a correction →