Binance

    Binance Hack: $6.3B by Binance's own estimate

    October 29, 2026 · Ethereum · TraderTraitor (DPRK), per the FBI

    Binance's estimate
    $6.3B
    in the largest single sweep
    167,464 ETH
    public price tags, $5.5B–$6.43B
    8
    frozen by Circle
    823M USDC

    What happened

    On 29 October 2026 funds began leaving Binance's hot wallets at about 20:05 UTC. Binance put the impact at about $6.3 billion; at least eight public estimates range from $5.5 billion to $6.43 billion, because they count different things. On Ethereum one operator address signed an EIP-7702 delegation on the Binance 14 hot wallet at 20:20:59 UTC and, at 20:24:23, moved 167,464.25 ETH and 63 token transfers, including 1,615,409,499 USDT, to a receiver with no earlier history; six more sweeps followed that evening, and Circle froze all 823,000,000 USDC that left this way. Funds from this theft and from September's Bitget exploit were reported combined at one Ethereum address after THORChain swaps; of its two feeders, the one on Bitcoin was sending before the Binance theft began.

    How the funds moved

    Step 1

    Rehearsal and delegation

    From 13:51 UTC the operator signed EIP-7702 delegations for three test wallets of its own and swept them; at 15:59 it deployed the sweeper contract. At 20:20:59 one type-4 transaction to Binance 14 carried 50 pre-signed authorizations.

    Step 2

    The sweeps

    At 20:24:23 one call moved 167,464.25 ETH and 63 token transfers out of Binance 14; six more sweeps followed until 23:56, and five calls between 23:36 and 23:54 succeeded but moved nothing. Both USDC sweeps, 823,000,000 in all, were frozen by Circle. Binance cleared the delegation at 00:10 UTC on 30 October.

    Step 3

    Commingling

    On 30 October funds from this theft and from September's Bitget exploit were reported combined at one Ethereum address after THORChain swaps. THORChain's own records show two feeders: a Bitcoin address that began sending on 23 October, six days before the theft, and a Tron address that appears only after it.

    Visualized attack path

    Binance Fund Flow Graph

    Key findings

    Price tags

    Eight public estimates, $5.5B to $6.43BThey differ in when the assets are priced, which wallets are counted and how much of the trace has been checked — none is an error. The blog piece lays them side by side.

    USDC

    823,000,000 USDC frozenThe two USDC sweeps add up to exactly 823,000,000, and the freeze is recorded at 21:04 UTC — every USDC that left Binance 14 this way was stopped.

    The Bitget link

    One feeder predates the theftThe Bitcoin feeder of the commingling address was sending into THORChain from 23 October, so it cannot be carrying Binance money. That is a fact about timestamps, not an attribution; the link to Bitget's wallets rests on public reporting.
    TIMESTAMPS, NOT ATTRIBUTION

    Issuer freezes

    Both addresses are frozen by their issuersThe receiver of the 167,464 ETH sweep carries Tether's USDT freeze, the commingling address Coinbase's cbBTC freeze — facts about the addresses, not an attribution of who controls them.

    Investigate your own incident

    Paste the address the funds left, and ChainHint follows them hop by hop.