Token Approvals: Permissions You Forgot You Gave
Old token approvals can let an app move your tokens long after you stopped using it. Learn how they get drained, how to find yours and how to revoke them.
Permissions you forgot you gave
Hi, I'm Block. Say you tried a token swap app once, a long time ago. You haven't opened it since. But it may still have permission to move those tokens out of your wallet, right now, without asking you again. In this lesson: what that permission is, how old ones get drained, and how to find and cancel yours.
This lives on the blockchain
Last time we cleaned up your setup: your email, your browser and your device. This one is different. Token approvals don't live on your computer at all. They live on the blockchain, so a new laptop or a fresh browser doesn't touch them.
Here's what an approval is. When you use an app to swap or lend tokens on networks like Ethereum, the app's smart contract needs permission to take those tokens from your wallet. So your wallet asks you to approve a spender, and an amount. Think of it like handing a valet a key to your car.
An approval is a key you hand to an app.
The rules come from the token standard itself. Once you approve a spender, it can pull tokens from your wallet again and again, up to the amount you approved, without asking you each time. That's what makes apps convenient. It's also exactly what makes approvals dangerous.
Convenient for apps. Dangerous if forgotten.
Do you have approvals?
Does this apply to you? Approvals belong to networks that run smart contracts, like Ethereum and the many networks built to work like it. If you've only ever bought coins on an exchange and held them there, you probably have none. But if you've ever clicked connect wallet on an app, you almost certainly have some.
Ever clicked connect wallet? You have approvals.
And here's the catch. Many apps ask for an unlimited amount, so you never have to approve again. Your wallet shows a request like this one. Look at the amount. Unlimited means every unit of that token you ever hold, not just what you're swapping right now.
And it doesn't expire on its own. The approval stays in place until you reduce it or cancel it, even if you never visit that app again, even if the project shuts down, even if it gets hacked years later. An approval doesn't remember that you forgot about it.
Forgotten by you. Still active on the chain.
There's a common mistake here. People click disconnect in their wallet and think the app's access is gone. It isn't. Disconnecting only stops the site from seeing your address. The approval is still sitting on the blockchain until you revoke it.
Disconnecting does not cancel an approval.
Two ways approvals get drained
So how do old approvals actually get drained? There are two main ways. Either a real app you approved gets hacked, or the app was never real in the first place. Let's look at both.
First, the real app that gets hacked. A popular bridging service added a new piece of code. Three days later, an attacker found a flaw in it and used it to pull tokens out of users' wallets, through the approvals those users had given. At least three point three million dollars was taken.
Months later, it happened again to a token swap service. Newly added code had a flaw, and about eleven million dollars was drained. The company said the only wallets affected were the ones set to unlimited approvals. People who had approved exact amounts weren't exposed.
Exact amounts weren't exposed.
Notice what those victims did wrong that day. Nothing. They didn't click a link or sign anything. The permission they'd given weeks or months earlier did the damage. That's why old approvals matter. You can be careful every single day and still be exposed by one you forgot.
Careful today can't fix a key you gave months ago.
The size of the approval matters too. A security researcher described it simply: if you bridge one thousand dollars but approve the app for two thousand, the extra thousand is sitting there exposed. Approve what you're using right now, and nothing more.
Approve what you're using right now.
Wallet drainers
The second way is the fake app. These are called wallet drainers. A fake site looks like a real swap, a free token claim or a mint. You connect, and the first thing it asks for is an approval. Sign it, and they don't need to hack anything. You handed them the key.
How do people end up on those sites? Often through a message like this one: a free token claim, a reward you supposedly earned, and a deadline. The link goes to a drainer, and the approval is waiting the moment you connect. Free money with a countdown is the bait.
Free money with a countdown is the bait.
One security firm that tracks drainers counted almost half a billion dollars taken from about three hundred thirty thousand victims in a single year. The next year was much lower, about eighty-four million from a hundred six thousand victims. That's real progress. But the trick still works on anyone who rushes.
Lower losses. Same trick.
And remember the fake search ads from last lesson? That's how a lot of drainer sites get their visitors. The crew behind those ads drained victims by getting them to approve tokens on look-alike sites. The approval request is the moment it all goes wrong.
Now the sneakiest version. Some tokens let you grant an approval with just a signature, called a permit. No transaction, no network fee. It feels like logging in. But that signature can set an approval for your whole balance, and the attacker submits it whenever they like.
No fee doesn't mean no risk.
How bad can one signature be? In the largest drainer case that security firm recorded in one year, a single permit signature led to the loss of about six and a half million dollars. If a site asks you to sign something you don't understand, close the tab.
Don't understand it? Don't sign it.
Hardware wallets and old approvals
What about hardware wallets? A hardware wallet protects your keys, and it makes you confirm each new approval on its screen. But once an approval exists, the spender can use it without your device being involved at all. Hardware wallets protect against new mistakes, not old permissions.
Old permissions skip the hardware wallet.
Find your approvals
Okay, enough bad news. Let's find your approvals and clean them up. You'll use an approval checker. Every major block explorer has one, and there are dedicated revoke tools too. For Ethereum, the Etherscan explorer has a token approval checker built in.
Get there the clean way, from a bookmark or by typing the address, inside the money profile we set up last time. Then connect your wallet or paste your address, and you'll see a list: each token, each spender, and how much it's allowed to take. You can paste your address just to look. Connecting is only needed to revoke.
Looking is free. Revoking needs a signature.
So what do you revoke? Start with anything unlimited. Then anything from an app you don't recognize, don't use anymore, or only tried once. Keep approvals for apps you actively use, and lower them where you can. When in doubt, revoke. You can always approve again later.
When in doubt, revoke. You can approve again later.
Here's what a cleanup looks like in practice. Say the checker shows three approvals: an unlimited one for a swap app you used once, one for a bridge you've forgotten, and one for the app you use every week. You revoke the first two, paying a small fee for each. The third you keep, but you lower it to what you actually need.
Revoke the old, lower the rest.
Two practical details. Revoking is a real transaction, so each one costs a small network fee. If a revoke ever asks for a big fee or a strange approval of its own, stop. And approvals are separate on every network, so check each network you've ever used, not just the main one.
Check every network you've ever used.
One warning about timing. Revoking closes the door for the future. It can't bring back tokens that are already gone. And fake revoke sites exist too, especially right after a big hack makes the news. After a hack, use your bookmark. Never a link from a reply or a message.
After a hack, use your bookmark.
Now let's stop new problems before they start. Many wallets let you edit the amount on an approval before you confirm it. Set it to what you're actually using. Read every request: if it says approve, permit or set approval for all, slow down. That last one gives access to every NFT in a whole collection.
Approve all means every NFT in the collection.
Here's a habit borrowed from security teams: a test wallet. Keep a separate wallet with a small amount for trying new apps, claims and mints. Your main savings never connect to anything new. If a test wallet gets drained, you lose pocket change, not your savings.
Lose pocket change, not your savings.
And make approval checks part of your routine. Every few months, open your checker and look again. Add one more check right after you hear about any hack involving an app you've used. Five minutes of cleanup can close doors you didn't know were open.
Five minutes closes doors you forgot were open.
Token approvals
Here's the whole lesson in four lines. An approval is a key you hand to an app, and it stays until you take it back. Disconnecting isn't revoking. Approve only what you're using, and never sign what you don't understand. And check your approvals every few months, on every network.
Every key you hand out, take back.
Sources
- ERC-20 standard: approve allows a spender to withdraw from your account multiple times, up to the approved amount; transferFrom lets contracts transfer tokens on your behalf
- Many protocols request unlimited approvals; approvals stay active until reduced or revoked on-chain; disconnecting a site does not affect existing approvals; a hardware wallet does not protect existing allowances; wallets can set a custom spending limit
- MetaMask: disconnecting a wallet from a dapp will not revoke any token approvals
- MetaMask: approvals often request unlimited access; use the approval checker on the block explorer for the network you're using; each revocation costs a gas fee; check approvals regularly
- Socket/Bungee (bridging aggregator) exploit, January 2024: a route added three days earlier was abused to drain wallets with infinite approvals to Socket contracts; at least $3.3 million; example of bridging $1,000 but approving $2,000
- LI.FI exploit, July 2024: about $11 million; newly deployed code had a flaw; the only wallets affected were set to infinite approvals
- Scam Sniffer: wallet-drainer phishing took $494M from about 332,000 victims in 2024 and $83.85M from 106,106 victims in 2025; largest 2025 case was $6.5M via a Permit signature; drainer signature types include Permit/Permit2, approve/increaseApproval and setApprovalForAll
- Permit (ERC-2612) sets an allowance from an off-chain signature; the signer pays no gas and sends no transaction; attackers used fake front-ends asking users to sign permits for their full balance
- Revoking via Etherscan's Token Approval Checker: connect, find the approval, click revoke and confirm; revoking and approving both require a gas fee
- An approval stays active even if the project shuts down or gets hacked; revoking should cost very little, and an unusually high fee is a warning sign
- MS Drainer exploited the token approval process on fake sites promoted with search ads
Education only. Not financial advice.
Education only. Not financial, investment, tax or legal advice. Block, our on-screen presenter, is AI-generated, voice included; the research and scripts are ours.