Skip to main content
WEB3 THREAT

Anatomy of a Crypto Drainer: How $1.93B Vanished in 6 Months

A drainer leaves your seed phrase alone and goes after your signature. A single click on the wrong "Claim", "Verify", or "Connect Wallet" button sets off a chain of pre-built smart contracts that empties your holdings before you can move your finger off the trackpad.

Editorial illustration: Anatomy of a Crypto Drainer: How $1.93B Vanished in 6 Months

In short

A crypto drainer is a Web3 phishing tool that targets your signature rather than your seed phrase. A fake dApp gets you to sign an approve(), setApprovalForAll() or off-chain Permit message that lets the attacker move your assets. The attack runs in six steps: lure, connect, recon, sign, drain and launder, and no authority can reverse its effect.

Key findings

H1 2025 losses, +540% vs 2023
$1.93B
lost by a single victim in January 20261
$284M
victims in 2023, ~900 every day
320K+
Inferno-related domains documented and reported
16,000+

A Trezor seed-phrase scam, not a drainer by the narrow definition.

On this page
$1.93B
H1 2025 losses
+540% vs 2023
$284M
Single victim, Jan 2026
Trezor seed-phrase scam
320K+
Victims in 2023
~900 every day
$5–10K
DaaS entry cost
turnkey kit

What a drainer actually is

Editorial illustration: Six-stage crypto drainer kill chain from lure to laundering

A crypto drainer is a phishing tool purpose-built for Web3. It doesn't try to phish your password or extract a private key. Instead it gets you to sign a transaction (usually an approve(), setApprovalForAll(), or an off-chain Permit message) that hands the attacker permission to move your assets at will. The wallet stays "yours" while the attacker empties it.

The model is brutally efficient because it abuses legitimate blockchain primitives. Your private key is never compromised, and there is no malware on your machine. All it takes is one signature on one transaction; on-chain analysts will see it, but no authority can reverse its effect.

According to Chainalysis, a drainer is "a phishing tool designed for the web3 ecosystem" that pretends to be a legitimate dApp. Group-IB, Check Point Research, and ScamSniffer have catalogued thousands of campaigns built on this exact mechanic.

The 6-step kill chain

Every drainer attack (Inferno, Pink, Angel, MS, CLINKSINK, Rugging, and the dozens of unnamed forks) follows the same six stages. The art is in compressing all of them into the seconds between a wallet connection and a confirmed transaction.

1 Lure airdrop / ad / DM 2 Connect wallet hooked 3 Recon analyzeWallet() 4 Sign approve / permit 5 Drain transferFrom() 6 Launder DEX → bridge → XMR SOCIAL ENGINEERING TECHNICAL EXECUTION EXFILTRATION

1. Lure

Fake airdrops, sponsored Google/X ads, compromised verified accounts (the SEC and Mandiant accounts have both been used as drainer megaphones), Discord verification bots, fake NFT mints, "exclusive" beta invites, and IP-licensing scams. Whatever the wrapper, the goal is to get you onto a domain the attacker controls.

2. Connect

You hit "Connect Wallet". Whether you use MetaMask, Rabby, WalletConnect, or Phantom, nothing about the prompt looks wrong. The drainer JavaScript now has read access to your wallet object via window.ethereum (or the equivalent), and starts firing eth_call requests in the background.

3. Recon

The drainer enumerates your holdings: native balance, ERC-20 tokens, NFT collections, DeFi positions across multiple chains. It hits CoinGecko-style price oracles to USD-rank everything. Premium kits like Inferno Drainer store their config on-chain (BNB Chain) so it can be updated without redeploying the JS payload.

4. Sign

The dApp prompts you to "Verify ownership", "Claim airdrop", "Approve collection", or "Sign to enter". Wallet UI shows what looks like a benign message. In reality the calldata is carefully chosen to maximize damage (see the next section).

5. Drain

The moment your signature lands, the attacker calls transferFrom() from a separate wallet (operational separation: the "Address" that received the approval is never the "Receiver" that holds the loot). Premium kits batch native ETH, ERC-20s, ERC-721/1155 NFTs, and Permit2 transfers in a single multicall. Funds start moving within seconds of the signature.

6. Launder

Funds route through SushiSwap / Uniswap (legitimate DEXs are deliberately allow-listed by most security tools), then through bridges to other chains, then through Tornado Cash forks, then to Monero. The $284M Trezor incident ended up in XMR within hours.

Your wallet (before signing)

ETH2.4815
USDC18,420.00
WBTC0.34
BAYC #42911 NFT
stETH12.1

Attacker contract (after one signature)

ETH+2.4815
USDC+18,420.00
WBTC+0.34
BAYC #4291+1 NFT
stETH+12.1

One signed Permit2 message can authorize the entire batch. There is no second confirmation and no recovery.

The four killer payloads

Every drainer in the wild uses some combination of these four primitives. Each one is a legitimate ERC standard or RPC method, so there is nothing to "patch" and awareness is the only defense.

1. approve(spender, type(uint256).max): ERC-20 unlimited spend

The classic. You approve a token contract for the maximum possible amount (2^256 − 1) to a spender address you don't control. The spender (that is, the attacker) then calls transferFrom(you, attacker, balance) at their leisure. The approval persists forever unless you explicitly revoke it via Revoke.cash or the token contract directly.

// What you actually signed:approve( 0xFc4a4858bafef54D1b1d7697bfb5c52F4c166976, // attacker0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff// max uint256 ) // Wallet UI showed: "Verify wallet ownership"

2. setApprovalForAll(operator, true): full NFT collection

It is worse than an ERC-20 approval because it is all-or-nothing per collection: one signature lets the attacker move every NFT in that contract. This is how Seth Green lost 4 Bored Apes in 2022 and how a single victim lost 14 BAYCs to the fake "Forte Pictures" licensing scam in December 2022.

setApprovalForAll( 0xattacker..., // "operator"true// approved for the entire collection )

3. EIP-2612 / Permit2 off-chain signatures

This is the 2024–2026 weapon of choice. Instead of an on-chain approve() (which costs gas and shows up clearly in your wallet), the attacker collects an off-chain EIP-712 signature via eth_signTypedData_v4. There is no transaction and you pay no gas; all you see is a pop-up that says "Sign this message". The wallet UI for typed-data signing is notoriously hard to read, and Uniswap's Permit2 turns one signature into approvals for multiple tokens at once.

// What MetaMask showed you:// "PermitSingle"// spender: 0x000000000022D473030F116dDEE9F6B43aC78BA3// ...looks fine, that's the real Permit2 contract...// What it actually authorized: { "details": { "token": "0xUSDC...", "amount": "1461501637330902918203684832716283019655932542975", // max"expiration": 281474976710655// year ~10889 }, "spender": "0xattacker...", "sigDeadline": 9999999999 }

See Blockaid's full Permit2 case study for a real attack walkthrough including the SushiSwap-routing trick that hides ETH drainage inside what looks like a normal swap.

4. Direct seed-phrase social engineering

Technically this is not a "drainer" by the narrow definition, but it is the highest-yield variant in 2026. The January 2026 Trezor incident didn't bypass any encryption. A "support agent" called the victim, walked them through a fake "verification" process, and got them to read out the recovery seed. The stolen funds, 1,459 BTC + 2.05M LTC = $284M or 71% of all crypto theft losses for that month, were converted to Monero before the news cycle picked up the story.

Hardware wallets prevent remote key extraction. They do not prevent you from typing your seed into a phisher's website. Use a BIP-39 passphrase.

The Drainer-as-a-Service economy

None of the actors who actually steal your money write the code; they rent it. Drainer-as-a-Service (DaaS) is a fully commoditized B2B market with branding, pricing tiers, support channels, version releases, and an obvious downward pressure on operator commissions.

Inferno
Most sophisticated. On-chain config (BNB), AES-encrypted C2, anti-debugger, SushiSwap routing. CP analysis
15–20% cut
Angel (GhostSec)
Multi-chain and productized, with versioned releases like commercial software (v8.2, v8.3...).
20% cut
CLINKSINK
JS-based, Solana-focused. The kit behind the Mandiant X hijack ($900K) and SEC compromise.
~20% cut
Pink
NFT-focused. Single-victim record: $320K in BAYC/MAYC/Otherdeed in one transaction.
~20% cut
MS Drainer
$59M from 63K victims via X (Twitter) sponsored ads, March–November 2023. ScamSniffer
var.
Rugging Multi-chain
Price-leader strategy: undercuts Angel/Inferno on commission to win volume.
5–10% cut

Entry cost for an affiliate: a $5,000–$10,000 deposit, sometimes a turnkey kit for the same. The affiliate keeps 75–95% of stolen funds and outsources every technical concern (JS payload, smart contract, hosting, laundering pipeline, even 24/7 Telegram support) to the operator. SentinelOne and the IMC 2025 academic study trace the supply chain in detail.

This is why one-off whack-a-mole takedowns aren't enough, and why registrars that ignore abuse are the actual bottleneck. PhishDestroy has documented and reported 16,000+ Inferno-related domains alone.

Red flags before you sign

The signature dialog is the last line of defense. If any of these are true, cancel, because no legitimate flow requires them:

  • You arrived via a sponsored search result, DM, or email link. Sponsored crypto results have been compromised at every major search engine. Always navigate from a bookmark.
  • The signature is "free" / "gasless" / "off-chain". That's a Permit2-style off-chain signature. Read the typed-data fields. If spender is unfamiliar, walk away.
  • The amount is uint256.max, 0xfff…fff, or "unlimited". Almost no legitimate flow needs unlimited approval.
  • The function is setApprovalForAll on a collection you don't recognize. Or for an "operator" that isn't OpenSea / Blur / LooksRare.
  • The site asks you to switch chains right after connecting. Multi-chain extraction loop in progress.
  • The destination contract was deployed less than 7 days ago. Inferno-class drainers rotate intermediate contracts every 24h.
  • You feel rushed. Every drainer template ships with countdown timers and lines like "claim ends in 4:32" or "only 12 spots left".
  • "Customer support" reached out to you first. None of Trezor, Ledger, MetaMask, Coinbase, or Binance will ever DM you.

Paste the request into the Signature Request Inspector to read the spender, amount and deadline in plain English before you sign.

How to actually defend yourself

  • Wallet segregation. Cold (hardware, majority of net worth) → operational hot wallet (1–2 weeks of activity) → burner wallet (anything new, near-zero balance). Never connect cold to a fresh dApp.
  • Hardware wallet + BIP-39 passphrase. The passphrase is the difference between "$284M Trezor incident" and "attacker has your seed and finds nothing". Memorize it. Don't store it digitally.
  • Transaction simulators.Blockaid, Wallet Guard, Pocket Universe, and Fire all show the actual balance delta before you sign. Install one.
  • Bookmark all dApps. Never type "uniswap" into Google. Never click crypto links from social media. The sponsored result is wrong far more often than you think.
  • Audit your approvals weekly.Revoke.cash shows every active allowance across every chain. Revoke anything you don't actively use.
  • Run any unfamiliar site through a burner first. Empty wallet, see what it asks for, then decide if it's worth a real wallet at all.
  • Disable browser extensions on the wallet profile. Use a separate browser profile (or a Brave Tor window) for Web3 only. Extensions are a documented drainer vector (see the Mend.io npm supply-chain analysis).
  • Check the domain reputation. Drop the URL into PhishDestroy domain reports, urlscan, or our Telegram bot. If we've already seen it, it's flagged.

If you already signed: do this in the next 60 seconds

  1. Stop. Don't sign anything else, including "fix" or "recovery" prompts. Those are second-stage scams piggybacking on your panic.
  2. Move whatever isn't drained yet. Generate a brand-new wallet (preferably hardware), and transfer the surviving assets to it. Highest value first. Treat every address derived from the compromised key as permanently burned.
  3. Revoke approvals on the compromised wallet via Revoke.cash on every chain, not just Ethereum. This is a race against the attacker's automation.
  4. Document everything. Tx hashes, attacker addresses, timestamps, the exact URL of the phishing site. Screenshot before clearing the tab.
  5. Report. File with FBI IC3, your local cybercrime unit, the affected protocols (Uniswap, OpenSea, etc., which sometimes freeze derivatives), and submit the phishing URL to @PhishDestroy_bot so we kill the infrastructure for the next victim.
  6. If a seed phrase was disclosed: the wallet is gone. Stop trying to "secure" it. Generate a fresh wallet, move on, and learn from what happened.

"A drainer never breaks the cryptography; it relies on the assumption that humans can read calldata at the speed wallets ask them to. Slow down by one signature, and the entire industry of theft collapses."

Sources & further reading

  1. Chainalysis, Crypto Drainers: A Web3 Threat
  2. Group-IB, Inferno Drainer Investigation
  3. Check Point Research, Inferno Drainer Reloaded
  4. ScamSniffer, Pink Drainer 2024 incidents
  5. Blockaid, Step-by-step breakdown of a crypto heist
  6. BleepingComputer, Mandiant X hijack via CLINKSINK
  7. Cyber Daily, Mandiant hijack = $900K campaign
  8. SentinelOne, The Rise of Drainer-as-a-Service
  9. Gurucul, Wallet approval abuse → malware-assisted Web3 attacks
  10. Mend.io, npm supply-chain attack on Web3 packages
  11. AInvest, January 2026 Trezor $284M analysis
  12. IMC 2025 academic, DaaS economy measurement study
  13. PhishDestroy, Registrars enabling global scams
  14. PhishDestroy, Anatomy of a phishing takedown
  15. PhishDestroy, Real-time destroy-list (85K+ active threats)

What PhishDestroy does about drainers

We are a non-profit operator collective. We hunt drainer infrastructure 24/7 across SEO, paid ads, Discord, X, Telegram, and registrar honeypots, then we kill it.

  • 231K+ phishing & scam domains tracked since 2019.
  • 231K+ abuse reports filed with registrars and hosts.
  • 50+ AV vendors and threat-intel platforms ingest our feed.
  • 0.20% confirmed false-positive rate: 469 of the 233,172 domains we have ever listed turned out to be legitimate after an appeal or an individual review.
  • Free, public, immutable evidence archive on GitHub (GitLab) + HuggingFace.

Spotted a drainer? Send the URL to @PhishDestroy_bot. We'll have the abuse report filed before your coffee gets cold.

#CryptoDrainer#Web3Security#WalletDrainer#Permit2#DaaS#Inferno

Share This Article

Transparency notice. PhishDestroy is a non-commercial, independent project. Our research may reflect an inherent bias against scam infrastructure and the services that enable it. Citations link to primary sources whenever possible — please evaluate independently. Nothing here is financial or legal advice. Read our full transparency statement →