# How to Check and Revoke Token Approvals on Ethereum and EVM Chains

Published 2026-10-22 · Crypto.world Team · Crypto.world

> A step-by-step guide to listing every token approval your address has granted on Ethereum and EVM chains, revoking the risky ones, and handling NFT, permit and Permit2 permissions, with a routine you can repeat.

## What an Approval Is: A Standing Allowance, Not a Payment

On Ethereum and other EVM chains, an ERC-20 token is a contract that keeps its own ledger of balances. To let a swap contract, a lending pool or a marketplace move some of your tokens, the standard uses two steps. You call `approve` on the token contract to grant an allowance, and the other party later calls `transferFrom` to pull tokens out of your balance, up to that allowance. Nothing leaves your wallet when you approve; the permission just sits on-chain until it is changed.

EIP-20, written by Fabian Vogelsteller and Vitalik Buterin and marked Final, defines the pieces: `approve(address _spender, uint256 _value)` sets the allowance, `allowance(address _owner, address _spender)` reads it, and `transferFrom` spends it. Of `transferFrom` it says the method "is used for a withdraw workflow, allowing contracts to transfer tokens on your behalf". On `approve` the text reads:

> Allows `_spender` to withdraw from your account multiple times, up to the `_value` amount. If this function is called again it overwrites the current allowance with `_value`.
>
>
>
> — Fabian Vogelsteller and Vitalik Buterin, authors, EIP-20: Token Standard (now titled ERC-20), Ethereum Improvement Proposals

Three facts follow from those two sentences. An allowance belongs to one token and one spender; "multiple times" makes it a standing permission; and a new call overwrites the old value, so an allowance of zero is no permission at all, and resetting it to zero is how a revoke works.

## Why Apps Ask for Unlimited Allowances, and What That Leaves Open

EIP-20 defines no special "unlimited" amount. By convention the largest `uint256` value, written `type(uint256).max` in Solidity, stands for it, and each token's code decides what that means. OpenZeppelin's ERC-20 contract states that when the value is the maximum, "the allowance is not updated on `transferFrom`", which it calls "semantically equivalent to an infinite approval".

Apps ask for it because every approval is a transaction that costs gas. Revoke.cash's explainer says that "many applications have opted to ask for unlimited approvals, which means that you only need to pay the approval's gas fee once."

MetaMask's help center agrees that large allowances make activity smoother, then states the cost: "having an unlimited token allowance in place may put you at risk of theft." If the dapp has a code flaw, attackers may be able to order it to withdraw your tokens, and if the site asking is a fake, "your tokens can be stolen as soon as you send the approval transaction."

MetaMask names two defences and calls the first the safest: never grant unlimited allowances, or grant them only to trusted sites and revoke them often. Its mobile prompt asks for a spending cap and offers a custom value, "Max" (the account's balance of that token) or "Use site suggestion". Where a wallet lets you type the cap, entering the amount you mean to spend limits the exposure to that amount.

## NFT Approvals and Signatures: setApprovalForAll, Permit and Permit2

ERC-721 NFTs have two approval levels. In EIP-721, `approve(address _approved, uint256 _tokenId)` covers a single token. `setApprovalForAll(address _operator, bool _approved)` is documented as "Enable or disable approval for a third party ("operator") to manage all of `msg.sender`'s assets", and `_approved` is "True if the operator is approved, false to revoke approval". ERC-1155 tokens have the same function.

ENS's support team calls `setApprovalForAll` the dangerous kind: "a blanket permission for every token in an NFT collection". Revoke.cash explains why it is common: a limited approval can go to only one address at a time, "and because of that, most NFT marketplaces use unlimited approvals."

A signature can also create an allowance with no approve transaction from you. ERC-2612 adds a `permit` function to a token, which "allows users to modify the `allowance` mapping using a signed message, instead of through `msg.sender`". The message is EIP-712 typed data naming owner, spender, value, nonce and deadline.

The spec adds: "The caller of the `permit` function can be any address." An app, a relayer or anyone holding your signature can therefore submit it, and the deadline can be set to `uint(-1)` "to create `Permit`s that effectively never expire". Because the signature is off-chain, Revoke.cash notes, a platform "can never determine which signatures you've signed", and the prompt can pass for a login.

Uniswap's Permit2 extends the idea to tokens without `permit`. Its documentation describes two modules: `AllowanceTransfer`, a standing, time-bound allowance with an amount and an expiration, and `SignatureTransfer`, a single transfer authorised by one signature that leaves no standing allowance. Before Permit2 can move a token, the user makes a one-time standard approval of the Permit2 contract on that token, "commonly for the maximum `uint256` amount". After that, a signature alone can create or change the Permit2 allowance for a given spender.

## What Drainers Collect: Scam Sniffer's Annual Report

Scam Sniffer, a scam-intelligence firm, defines signature phishing as attacks that "trick victims into signing malicious transactions (approve, permit, setApprovalForAll, etc.) through phishing websites". Its annual report, published on 3 January 2026, covers 2025 on EVM chains. It counts $83.85 million lost across 106,106 victims, down 83% and 68% respectively from 2024. The largest single theft was $6.5 million in September, made with a Permit signature, and Permit and Permit2 signatures accounted for 38% of the losses in cases of $1 million or more.

The report calls its figures a lower bound: they cover wallet-drainer phishing sites only and exclude direct hacks, exchange compromises and contract exploits. It attributes the swings to market activity, with losses peaking in the third quarter, and warns that falling totals do not mean the threat is gone. Drainers ask for the same permissions this guide covers.

## Step by Step: List Every Approval Your Address Has Granted

Approvals belong to an address on a specific chain, so the list has to be read per address and per chain.

1. **Write down your addresses and chains.** Include every wallet address you have signed from, and every network, such as Ethereum, a layer 2 or a sidechain. ENS's help page notes that approvals are per-chain and must be checked network by network.
2. **Reach the tool without following a link.** Etherscan's checker is at etherscan.io/tokenapprovalchecker, and the explorers of other chains, such as BscScan and Polygonscan, have an equivalent page, as MetaMask and Revoke.cash document. Type the address or use a bookmark. Blockaid (30 April 2026) reports drainers registering lookalike "revoke" domains after exploits, where the user "connects their wallet expecting to revoke permissions, and instead signs a transaction that hands the drainer everything." A PhishFort article on Revoke.cash's blog (25 June 2026) counts more than 60 domains impersonating Revoke alone.
3. **Load the address.** Etherscan's page asks you to connect a wallet (the button read Connect Wallet when this guide was written; older guides call it Connect to Web3). Revoke.cash also accepts a pasted address or ENS name. Connecting shares your address and balances; MetaMask treats it as a different thing from an allowance.
4. **Pick the token type.** Etherscan's page has ERC-20, ERC-721 and ERC-1155 tabs. Revoke.cash's walkthrough of that page says to switch on "Show all approvals" so nothing is hidden; look for it if the list seems short.
5. **Read each row as three facts.** Etherscan prints the token under "Assets", the spender under "Approved Spender", and the allowance, plus "Last Updated (UTC)". Its page explains: "The at risk amount shows what is vulnerable if the contracts were hacked." On Revoke.cash you can sort, filter, or search by spender address, and sorting "Newest to Oldest" shows recent grants first, the order to use after signing something suspicious.
6. **Mark what to remove.** Start with spenders you cannot name, especially collection-wide NFT approvals (ENS calls these the priority), then collection-wide approvals you no longer need, unlimited allowances on tokens you hold in size, and apps you have stopped using.

## Step by Step: Revoke One Approval and Confirm It Worked

A revoke is the grant with the value zeroed. Revoke.cash states that for fungible tokens it is done "by calling approve() again with the same parameters, but with the amount set to 0", and for collection-wide NFT approvals by calling `setApprovalForAll` with false. That matches EIP-20, where a new `approve` overwrites the old value. EIP-20 also says client interfaces SHOULD set an allowance to `0` before changing it to another value for the same spender, to close a known attack.

1. **Select the approval and press the revoke control.** On Etherscan that is the row's Revoke action (the page also prints a Revoke Selected button); on Revoke.cash it is the Revoke button. Revoke.cash also has a pencil icon beside the amount to lower it instead, which suits an app you still use.
2. **Read the wallet prompt before signing.** A genuine revoke removes a permission, so a prompt that grants an amount or sets approval-for-all to true is not one. A PhishFort article on Revoke.cash's blog warns that a fake site's transaction "adds a new malicious approval". If the prompt grants something, reject it.
3. **Pay the gas.** MetaMask states that because approvals are on-chain, revoking "must also be on-chain", with gas "for each revocation". ENS adds that it is one transaction per approval and that the gas paid to grant the original approval is not refunded. Keep a little of the chain's gas token in the wallet.
4. **Wait, then reload the list.** OpenSea's help article says the approval is revoked once the transaction completes. The next time you use that app it will ask again, and OpenSea notes an NFT cannot be bought, sold or transferred through its services until the allowance is granted again. Set a cap this time.

## Permit2, Unspent Signatures and What Revoking Cannot Undo

Permit2 has two layers to clear. The first is the ordinary approval of the Permit2 contract on each token; Revoke.cash recommends revoking it when you no longer use Permit2, given the added phishing risk. Uniswap documents the contract at `0x000000000022D473030F116dDEE9F6B43aC78BA3` on every chain it supports except zkSync, which has its own address; a spender with that address in your list is this first layer.

The second layer is the allowances Permit2 grants to individual spenders, each with an expiration. Uniswap's documentation says that passing `0` as the expiration "expires permissions at `block.timestamp`", and its contract source includes a `lockdown` function for "batch revoking approvals". Revoke.cash says to let near-term expirations lapse and to revoke or update any set too far ahead.

A signed permit that nobody has submitted yet is harder to deal with. Revoke.cash writes that cancelling a signature before the scammer submits it is "generally very hard", because scammers try to activate it at once; once activated, it can be revoked like a regular approval. ERC-2612 itself notes that a signer who submits a permit first can make previously signed permits invalid. Revoke.cash has a Signatures tab for attempting a cancellation, but its list is only of potential signatures, since the tool cannot see what you signed.

Revoking removes a permission and reverses nothing already done. ENS's help page says it "doesn't undo transfers that already happened", and a leaked seed phrase is beyond it: anyone holding the phrase "can re-grant any approval you revoke". Revoke.cash's seed-phrase article puts it as "No revoking", and advises moving funds to a fresh wallet.

A hardware wallet keeps the private keys offline, as Revoke.cash puts it, but an approval still involves a transaction or message that key signs, so its owner needs the same check. Trezor's support page separates disconnecting a dapp (it can no longer see the address and balances) from revoking approvals, and points to third-party tools for the latter.

Approval lists cover approvals only. Etherscan's page says it lists "contracts that have been approved to spend an address's tokens", while Scam Sniffer's report counts other signature types, such as EIP-7702 batches, as separate cases. A clean list therefore does not cover every signature a wallet can be drained through.

## A Routine Check to Repeat

MetaMask suggests developing "a habit of regularly checking your token approvals—e.g. monthly". A repeatable pass for each address:

1. Open the checker from a bookmark, for each address and each chain on your list.
2. Sort newest first and look at anything granted since the last pass; revoke what you cannot explain.
3. Revoke collection-wide NFT approvals after a sale, and the Permit2 contract approval on tokens you no longer trade.
4. When you do approve, type a cap in place of the maximum, and run the pass again after any app you used is reported hacked.

Keep the list of addresses and chains beside the bookmark, and date each pass.

## Sources

1. [EIP-20: Token Standard (Ethereum Improvement Proposals)](https://eips.ethereum.org/EIPS/eip-20) eips.ethereum.org
2. [EIP-721: Non-Fungible Token Standard (Ethereum Improvement Proposals)](https://eips.ethereum.org/EIPS/eip-721) eips.ethereum.org
3. [EIP-1155: Multi Token Standard (Ethereum Improvement Proposals)](https://eips.ethereum.org/EIPS/eip-1155) eips.ethereum.org
4. [EIP-2612: Permit Extension for EIP-20 Signed Approvals (Ethereum Improvement Proposals)](https://eips.ethereum.org/EIPS/eip-2612) eips.ethereum.org
5. [OpenZeppelin Contracts: ERC20.sol (source)](https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/token/ERC20/ERC20.sol) github.com
6. [Uniswap Docs: Permit2 Overview](https://developers.uniswap.org/docs/protocols/permit2/overview) developers.uniswap.org
7. [Uniswap Docs: Permit2 Allowance Transfer](https://developers.uniswap.org/docs/protocols/permit2/concepts/allowance-transfer) developers.uniswap.org
8. [Uniswap Permit2: IAllowanceTransfer.sol (source)](https://github.com/Uniswap/permit2/blob/main/src/interfaces/IAllowanceTransfer.sol) github.com
9. [Cosmos EVM Docs: Permit2 predeployed contract (address cross-check)](https://docs.cosmos.network/evm/v0.4.x/documentation/smart-contracts/predeployed-contracts/permit2.md) docs.cosmos.network
10. [Etherscan: Token Approval Checker](https://etherscan.io/tokenapprovalchecker) etherscan.io
11. [Scam Sniffer: 2025 report, Crypto Phishing Losses Fall 83% to $84 Million (3 January 2026)](https://drops.scamsniffer.io/scam-sniffer-2025-crypto-phishing-losses-fall-83-to-84-million/) drops.scamsniffer.io
12. [CoinCentral: Scam Sniffer, Crypto Phishing Losses Fall to $83M in 2025 (cross-check)](https://coincentral.com/scam-sniffer-crypto-phishing-losses-fall-to-83m-in-2025/) coincentral.com
13. [MetaMask Help Center: How to customize token approvals with a spending cap](https://support.metamask.io/configure/tokens/how-to-customize-token-approvals-with-a-spending-cap) support.metamask.io
14. [MetaMask Help Center: How to revoke smart contract allowances/token approvals](https://support.metamask.io/more-web3/learn/how-to-revoke-smart-contract-allowances-token-approvals) support.metamask.io
15. [ENS Help Center: Revoke token approvals](https://support.ens.domains/en/articles/8799777) support.ens.domains
16. [OpenSea Help Center: How can I revoke token approvals and permissions on Ethereum?](https://support.opensea.io/en/articles/8867133-how-can-i-revoke-token-approvals-and-permissions-on-ethereum) support.opensea.io
17. [Revoke.cash Learn: What Are Token Approvals?](https://revoke.cash/learn/approvals/what-are-token-approvals) revoke.cash
18. [Revoke.cash Learn: How to Revoke Token Approvals and Permissions](https://revoke.cash/learn/approvals/how-to-revoke-token-approvals) revoke.cash
19. [Revoke.cash Learn: What Are EIP2612 Permit Signatures?](https://revoke.cash/learn/approvals/what-are-eip2612-permit-signatures) revoke.cash
20. [Revoke.cash Learn: What Is Permit2?](https://revoke.cash/learn/approvals/what-is-permit2) revoke.cash
21. [Revoke.cash Learn: Seed Phrase Compromise](https://revoke.cash/learn/security/seed-phrase-compromise) revoke.cash
22. [Revoke.cash Blog (PhishFort Team, 25 June 2026): How to Verify You're on the Real Revoke.cash](https://revoke.cash/blog/2026/how-to-verify-revoke-cash-legitimate) revoke.cash
23. [Blockaid (30 April 2026): How wallet drainers use fake revoke sites and Twitter phishing to exploit victims](https://blockaid.io/blog/how-wallet-drainers-use-fake-revoke-sites-and-twitter-phishing-to-exploit-victims) blockaid.io
24. [Trezor Guides: Revoke smart contracts and allowances](https://trezor.io/guides/third-party-wallet-apps/ethereum-evm-apps/revoke-smart-contracts-and-allowances) trezor.io

## Companies in this story

- [Uniswap Labs](https://crypto.world/companies/uniswap-labs)

## Related stories

- [How to Run a Bitcoin Full Node at Home](https://crypto.world/implementation/how-to-run-a-bitcoin-full-node-at-home)
- [How to Write, Test and Deploy Your First Smart Contract on an Ethereum Testnet](https://crypto.world/implementation/how-to-write-test-deploy-first-smart-contract-ethereum-testnet)
- [How to Check Whether a Crypto Company Is MiCA-Authorised](https://crypto.world/implementation/check-crypto-company-mica-authorisation)

## Explore

[More articles](https://crypto.world/implementation)

---

Canonical: https://crypto.world/implementation/how-to-check-and-revoke-token-approvals-ethereum-evm
