Loading prices…

Crypto Wallet Drainer Kits in 2026: How They Actually Work

Drainer kits now target permit2, session keys, and smart accounts, not just legacy approvals. Here is the current taxonomy and the laundering trail behind it.

Crypto Wallet Drainer Kits in 2026: How They Actually Work

What a crypto wallet drainer actually is in 2026

A wallet drainer is a piece of software, usually JavaScript loaded from a phishing site, that convinces a user to sign one or more on-chain messages or transactions that hand an attacker the ability to move specific assets out of that wallet. The word 'drainer' replaced the older term 'crypto stealer' around 2022 because the modern kits rarely break cryptography or break into the wallet app itself. Instead, they trick the human at the keyboard into signing the wrong thing, then automate the theft.

By 2026, drainers are no longer bespoke malware. They are subscription services. Operators rent dashboard access for anywhere from a few hundred to several thousand dollars a week, get a kit that runs in the browser, a Telegram support channel, and a share of the take. The most widely tracked brand, Inferno, publicly retired in late 2023, but its design templates continue to circulate as forks, and successor brands like Pink, Angel, and Venom dominate current forums.

Two facts matter for the rest of this taxonomy. First, every drainer in circulation today is built around one or more 'approval primitives,' the on-chain mechanisms that let a smart contract move tokens on a user's behalf. Second, after the theft is signed, the laundering path is almost entirely automated. Both halves are why a defense that worked in 2022, 'just revoke your approvals afterward,' is now too slow and too narrow.

The risks: what actually goes wrong for victims

The first risk is the obvious one: total loss of the drained assets. On ETH, an approval that goes wrong can empty every ERC-20 and ERC-721 in the wallet that the approval covers, and on smart accounts, a session key can drain the entire smart-account contract in a single block. SOL drains are usually narrower because Solana's token-2022 and system-program approval model is more constrained, but seed-phrase-exfil kits still wipe native SOL and SPL balances.

The second risk is downstream. Once a drainer operator controls a wallet, they can use it as a money-laundering hop, signing further transactions that link the victim's address to scams, sanctions, or even criminal investigations. Victims have found their wallets frozen by centralized exchanges simply because an attacker routed funds through them, even when the victim never withdrew the funds.

The third risk is reputational and legal. Signing a malicious message does not, in most jurisdictions, absolve a user of the resulting transfers. Several 2024-2025 enforcement actions treated drained wallets as the originating address for downstream fraud. Recoveries are rare. Reimbursements from hardware wallet makers cover a small set of hardware-level attacks, not social engineering. Treat every drainer signature as irreversible on-chain.

How drainer kits reach victims in 2026

The distribution layer has consolidated. Telegram and X are the two largest channels, with YouTube comment sections and Discord raids a distant third. The playbook is consistent: a fake account impersonates a known journalist, project founder, or VC, posts a 'surprise airdrop,' 'stealth mint,' or 'claim page,' and replies under every popular post in a category to harvest clicks.

The bait site is built to look like a legitimate dapp. It may clone the OpenSea mint page, the Uniswap swap UI, or a memecoin launchpad. Most critically, it is fully wallet-aware. The site asks the user's wallet to connect, reads which chain and which address class it sees, and serves the matching drainer flow. An Ethereum address running a Safe (now known as Safe{'{Wallet}'}) contract sees a different script than an EOA. A Solana address gets a different script than a Phantom user with Ethereum assets hidden in the same key.

The hosting layer is fast-moving. Domains are aged for weeks, fronted by Cloudflare, and rotated hourly. Some kits ship a 'landing page generator' that produces hundreds of lookalikes from a single template, each with a unique title and meta description to defeat naive brand-protection scraping. The result is that blacklists are always one step behind, which is why user-level skepticism matters more than ever.

The 2026 approval-primitive taxonomy

Drainers are best understood by the approval primitive they exploit. Below are the four primitives that matter right now, ordered from oldest to newest. Each section describes the exact on-chain mechanism, the bait that tricks the user into signing it, and what it lets the attacker do once signed.

Legacy setApprovalForAll on ERC-721 and ERC-1155

This is the classic NFT drain. ERC-721 and ERC-1155 contracts expose a setApprovalForAll function that, when called by a user, lets an operator contract move every token from that collection on the user's behalf. The bait usually looks like a free mint, a 'claim your airdrop' page, or a fake OpenSea listing. The victim sees a wallet prompt that looks identical to a normal marketplace approval and clicks confirm. The attacker then calls transferFrom in a loop until every NFT in that collection is gone.

Why it still works in 2026: many users have already approved marketplaces like OpenSea, Blur, or LooksRare in the past, and have stopped checking what setApprovalForAll actually does. Drainers also chain this with a token approval in the same transaction, so a single click signs two or three distinct drains.

The approval-setMax + transferFrom flow on ERC-20

This is the workhorse drain for ETH and EVM chains. The victim signs an approve call granting a malicious spender 'setMax' (in practice, type(uint256).max, an astronomically large number) on a specific ERC-20, often wrapped ETH, USDC, USDT, or a stablecoin sitting in the wallet. The wallet UI may show the approval in human-readable form, but humans tend to skim it.

Once the approval is mined, the attacker calls transferFrom against the victim's address, sweeping the balance to a contract they control. This is the flow behind the 'revoke your approvals' advice that dominated 2022-2023. The advice was correct for its time. It is no longer sufficient because newer primitives let the drain happen in the same block as the signature, before any human could revoke.

eth_sign legacy traps

eth_sign is a pre-EIP-191 signature method that signs arbitrary bytes with an Ethereum account. It does not include any structured data, so the wallet cannot display a human-readable summary. Drainers abuse eth_sign to get victims to sign messages that look like ordinary login signatures ('Click sign to verify you own this wallet') but are actually 32-byte hashes of structured permits or off-chain orders.

Although most modern wallets have removed eth_sign or warn loudly about it, phishing kits still surface it because enough niche wallets and bridge frontends still accept it. The defense is straightforward: never sign an eth_sign prompt you did not initiate from a trusted dapp. Treat eth_sign as 'sign anything the attacker wants.'

permit2 universal approvals

Permit2 is a contract pattern, popularized by Uniswap and now deployed across many DEXes, that replaces per-token approve calls with a single signature-based approval covering many tokens at once. The bait page asks the victim to sign a PermitSingle or PermitBatch message, often for a 30-day or unlimited window. Most wallets display this clearly, but the message is dense, and users acculturated to clicking through swaps do click through permits.

Why permit2 is dangerous: the signed permit can include a list of tokens the user holds that the drainer has observed via public RPC calls. Once signed, the drainer can call transferFrom against permit2 and sweep every whitelisted token in a single transaction, even tokens the user did not previously interact with. 'Revoke the permit2 approval afterward' is technically correct, but the drain happens inside the same block as the phishing click.

Session-key drains on smart accounts

Smart accounts, including Safe{'{Wallet}'} and ERC-4337 account abstractions, support session keys: scoped, time-limited authorizations that let a dapp perform a defined set of actions on behalf of the user. Drainers targeting smart accounts try to trick users into signing a session-key grant whose scope is set to 'everything for 24 hours' or 'unlimited for this session.' The wallet UI may render this as a long string of permissions that the user accepts to 'use the dapp.'

The drain that follows is brutal: a single UserOperation can call the smart account's execute function in a loop, draining every asset the smart account holds, across every token class, before the user closes the tab. By the time the user opens a revoke tool, the assets are three bridges away.

What the laundering trail looks like

Theft is only half of a drainer's job. The other half is making the funds untraceable, fast, before exchanges freeze them or analytics firms flag them. The 2026 laundering stack is layered.

Layer one is the contract hop. Within seconds of the drain, the stolen ETH or SOL is moved through a sequence of attacker-controlled contracts. Each contract unwraps, swaps, and repackages the assets, often using Uniswap v3, v4, or a fork on EVM chains, and Raydium or Jupiter on Solana. Each hop severs the simple 'funds went from A to B' trail that basic explorers can follow.

Layer two is the cross-chain bridge or swap-based mixer. Bridges like Wormhole, LayerZero, and Stargate remain common, despite their own on-chain analytics. Swap-based mixers, which use repeated small swaps across many pools to break traceability, have largely replaced Tornado Cash for SOL drains. Some drainers use THORChain or similar cross-chain swap protocols specifically because they settle in different assets on different chains, which complicates attribution.

Layer three is the off-ramp. Funds ultimately land in OTC desks, non-KYC centralized exchanges, or directly in stablecoin bank off-ramps where KYC is lax. A non-trivial share of 2024-2025 drainer proceeds ended up at over-the-counter services in jurisdictions with weak AML enforcement, then in fiat bank accounts in higher-KYC jurisdictions where the funds are indistinguishable from legitimate wealth.

For the victim, the practical consequence is brutal: the 30-second window between signing the malicious message and the assets being untraceable is shorter than the time it takes to find and click a 'revoke' button. By the time any human reacts, the funds are already laundered.

Practical implications for your wallet

The first implication is that 'revoke afterward' is now a last resort, not a primary defense. Treat every wallet signature, not every on-chain approval, as the dangerous moment. If you do not understand what a wallet popup is asking you to sign, close the tab. The cost of a missed mint is zero. The cost of a wrong signature is your wallet.

The second implication is that not all wallets are equal against drainers. Hardware wallets and modern smart-contract wallets that simulate every signature and render human-readable summaries of EIP-712 typed data (the structured signature format used by permit, permit2, and most dapps) catch more drainers than legacy wallets that surface raw transaction calldata. On ETH, prefer wallets that decode EIP-712 in clear language. On SOL, prefer wallets that show the destination program and any token accounts a transaction will touch.

The third implication is that transaction simulation is no longer optional. The leading wallets now simulate every transaction against a forked state and warn if the simulation results differ from the visible intent ('you are about to approve unlimited USDC to a contract that is not USDC'). Users who enable simulation warnings catch a meaningful share of drainers before signing. Users who ignore them do not.

The fourth implication is that bait-site discipline matters more than ever. The phishing sites are good. They look like the real dapps. The only reliable signals are contextual: was this link shared by a verified account, did you navigate to the URL yourself, and is the dapp's domain one you have used before. Skepticism is a feature, not a bug.

How to follow wallet-drainer news the smart way

Drainer kits evolve fast. New approval primitives, new bait patterns, and new laundering routes appear every quarter, and the gap between 'kit released' and 'first victims drained' is now measured in days. Tracking this manually, across Telegram channels, X feeds, GitHub repos, and on-chain analytics dashboards, is a losing game for any individual user. Zippfeed surfaces crypto wallet-drainer and security headlines with sentiment scoring (bullish, neutral, or bearish) and an importance rating, so you can spot the next approval-primitive exploit before it reaches your timeline.

Frequently asked questions

Is it safe to connect my wallet to a new site to claim an airdrop?
Generally no. Airdrop claim sites are one of the top bait vectors for drainer kits in 2026, and the claim page may ask you to sign a permit, permit2, or session-key grant that drains your wallet. Only connect to URLs you have verified through an independent channel, and treat every signature request as the dangerous step, not the connect step.
How does a crypto wallet drainer kit actually work?
A drainer kit is a piece of JavaScript loaded by a phishing site that reads your connected wallet, picks an approval primitive the wallet supports (setApprovalForAll for NFTs, approve for ERC-20s, permit or permit2 signatures, or session keys for smart accounts), and tricks you into signing the matching message. Once signed, the kit's backend calls transferFrom or execute in a loop to sweep the targeted assets, then routes them through bridges, mixers, and OTC desks.
Should I revoke old token and NFT approvals after this?
Revoking is reasonable hygiene, but in 2026 it is no longer the primary defense against drainers. Modern drainers using permit, permit2, and session keys complete the theft inside the same block as the malicious signature, so a user-driven revoke almost always loses the race. Focus your effort on not signing malicious messages in the first place; treat revocation as cleanup, not protection.
What are permit2 and session keys, and why do drainers prefer them?
Permit2 is a contract pattern that lets a user approve many tokens at once via a single EIP-712 signature, and session keys are scoped, time-limited authorizations used by smart accounts. Drainers prefer both because a single signature can authorize the movement of many tokens or many actions, and because the drain happens in the same transaction as the signature, before a user can react. Education, not financial advice: understanding these primitives is the strongest individual defense available today.
Related tokens
$ETH $SOL