← back to blog

Recovering After You Sign a Wallet Drainer Approval

If you just signed something you shouldn’t have and your wallet is draining, or already drained, stop reading tips threads and do the two things that actually matter: check what’s still approved, and revoke it. Everything else, including whether anything can be recovered, comes after that. This isn’t a scare piece. It’s what to actually do, in order, and why each step works the way it does.

What a drainer approval actually does

Most wallet drainers don’t steal your seed phrase. They get you to sign a transaction that grants a smart contract permission to move your tokens on your behalf. That’s it. It’s the same mechanism every legitimate dApp uses when you approve a token spend, except the contract on the other end is malicious.

There are a few common forms:

  • ERC-20 approve: you grant a contract an allowance to spend a specific token, sometimes for an unlimited amount. A drainer with this approval can pull that token out whenever it wants, not just once.
  • setApprovalForAll on NFTs: you grant a contract control over your entire NFT collection in that contract, not one token. This is the one that empties whole PFP holdings in a single click.
  • Off-chain signatures like permit or Permit2: you sign a message, not a transaction, so it doesn’t cost gas and it doesn’t show up as clearly in your wallet’s confirmation screen. The drainer then submits the actual transfer on your behalf later, sometimes days after you signed.

The distinction that matters most: if you only signed an approval, your seed phrase and private key are still yours. The attacker has permission over specific assets in specific contracts, not control of the wallet itself. If you also entered your seed phrase somewhere, that’s a different and worse problem, and revoking approvals won’t fix it, because the attacker can just re-sign anything they want.

Check whether it’s still active

Before doing anything else, find out what’s actually approved right now. Use a block explorer’s token approval checker for the chain you’re on (Etherscan, BscScan, and most major explorers have one built in), or a dedicated tool like revoke.cash. Connect the wallet in read-only mode if the tool offers it, and look at the list of active approvals: which contract, which token, and whether the allowance is capped or unlimited.

If a drainer contract shows up with an active allowance, assume it will use it the moment there’s a balance worth taking. Drainers often watch approved wallets and sweep new deposits automatically, so “it hasn’t taken anything yet” doesn’t mean you’re safe, it might mean the wallet is currently empty.

Revoke the approval

Revoking sends a new transaction that sets the allowance back to zero, or removes the operator status for NFTs. It costs gas, same as any other transaction, and you pay that gas from the compromised wallet, which is one more reason to move fast if there’s any native token left in it to cover the fee.

Do this for every suspicious or unrecognized approval, not just the one you think is the drainer. Some drainer kits set multiple approvals in the same signing flow, one to look legitimate and others buried in the same batch. If you’re not sure whether an approval is legitimate, revoke it anyway; a real dApp will just ask you to re-approve next time you use it, which costs a few dollars in gas and nothing else.

If the wallet has no native token left to pay for the revoke transaction, you have two options: send a small amount of gas token in from another wallet you control, or use a gas-sponsorship / meta-transaction service if the chain supports one. Either way, the revoke transaction needs to land before the drainer’s sweep does, so treat it as the priority, not an afterthought.

If funds already moved

Once tokens are out of the wallet, revoking stops future losses but doesn’t bring anything back. On-chain transfers aren’t reversible, and there’s no support desk to call. What’s realistic to do:

  • Trace where it went. Follow the transaction on a block explorer. If funds landed in a wallet that later deposited to a centralized exchange, that exchange has a compliance team that can freeze funds if you file a report with enough detail, though this depends entirely on the exchange and how fast the attacker moves the funds onward.
  • File a report. For US-based losses, IC3 (the FBI’s Internet Crime Complaint Center) takes crypto theft reports and does sometimes correlate them across cases. This is about building a paper trail, not a guarantee of recovery.
  • Don’t pay “recovery services.” Anyone who messages you offering to recover stolen crypto for an upfront fee is almost always running a second scam on top of the first. Legitimate investigators don’t cold-DM theft victims.

None of this is a promise you’ll get anything back. Most drained funds are gone. The value in doing it anyway is closing the loop and having a record, not expecting a refund.

Isolate the wallet, don’t reuse it

Once a wallet has interacted with a drainer contract, treat it as burned for anything beyond finishing the revoke cleanup. Move any remaining legitimate assets to a fresh wallet with a new seed phrase, generated on a device you trust. Don’t just “clean up” the same address and keep using it.

This matters more if you’re running multiple wallets for airdrop farming rather than a single holding wallet. A compromised wallet’s transaction history doesn’t just carry theft risk, it also becomes a fixed point that chain analysis can anchor to. If that wallet ever interacted with others in your set (a shared funding source, a batch transfer, a common exchange withdrawal), an analyst clustering wallets by shared inputs or funding patterns now has one compromised, well-documented node to work outward from. Keeping farming wallets funded and operated independently of each other isn’t just about avoiding sybil flags, it also limits how much a single security incident can expose.

Building better habits from here

A few concrete things that reduce how often this happens again, none of them exotic:

  • Split by risk, not convenience. Keep a wallet for signing new or unfamiliar contracts separate from wallets holding anything you’d be upset to lose. A drainer approval on a wallet with $40 in it is an annoyance. On your main holdings, it’s not.
  • Read what you’re signing. Wallets like Rabby show a plain-language simulation of what a transaction will actually do before you confirm it, including which assets move and to where. It’s not foolproof, but it catches the “this approves your entire NFT collection to an unknown contract” case that a raw signature request won’t show you.
  • Check approvals periodically, not just after an incident. Old approvals to dApps you stopped using are dead weight. A five-minute pass through a token approval checker every so often costs nothing and shrinks your exposure.
  • Treat unsolicited mint links, airdrop claim pages, and “connect wallet to check eligibility” sites with the same suspicion you’d give an unsolicited email attachment. Real airdrop claims are announced through a project’s official channels, not a random link in your Discord DMs.

None of this makes you unhackable. It makes a mistake cost you one wallet instead of your whole farm.

If you’re building out multiple wallets for airdrop farming and want to see how we structure isolation, funding, and approval hygiene across a real operation, head back to the Airdrop Farming homepage for the rest of our wallet ops and tooling breakdowns.

Get new guides and videos first — join the Telegram channel.

need infra for this today?