
Hypernative · 2026-10-29 22:38 UTC
Onchain data now confirms Binance hot wallets were drained. Here's what we know so far: → From about 20:10 UTC, Binance hot wallets on Ethereum, Arbitrum, Optimism, Base, Solana and Bitcoin, and likely Tron and Avalanche, sent funds to fresh attacker addresses. → Losses are $3.6B+, with public estimates up to ~$5.8B. → Every outflow was authorized with the hot wallets' own keys . How the attacker got signing access is not yet known. → On Ethereum, Binance 14 was taken over with EIP-7702 and is still delegated to the attacker's contract. → Tether and Circle have frozen part of the stolen USDT and USDC. ETH, SOL, BTC and most other tokens can't be frozen and some are already moving. Timeline (UTC) 1️⃣ 02:28: The attacker deploys a test version of a drainer contract. 2️⃣ 15:59: The drainer contract goes live. Only the attacker can call it. 3️⃣ ~20:10: Binance hot wallets begin sending funds to attacker addresses. 4️⃣ 20:20: One transaction carrying 50 pre-signed authorizations from Binance 14 delegates the wallet to the drainer contract. 5️⃣ 20:24: A single call sweeps ~167K ETH and ~64 tokens from Binance 14. 6️⃣ 20:41 and 20:59: The same delegation is used to move ~$823M USDC out of another Binance contract. 7️⃣ 21:04: Binance 14 is swept again. 8️⃣ Since then: USDT was swapped to ETH ahead of the freezes, and BTC is being split into 1,000 BTC chunks. What to do → Keep exposure to Binance reduced until Binance confirms its hot wallets are secure. → Do not send funds to Binance 14 (0x28c6c06298d514db089934071355e5743bf21d60). It is still delegated to the attacker's contract, so anything that arrives there can be swept. → Exchanges, OTC desks, bridges and other venues taking deposits: screen and block inbound funds from the attacker address (0x5227f603c1ee34ce3c06efe6477003bdfccb2f8c).
Loading the story on Tree News…