Binance is gradually resuming withdrawals following a hacker attack that stole around $6.3 billion. Spot.uz reports this, citing the crypto exchange’s official X account.
The hack occurred on the night of October 30, 2026. According to preliminary data cited by Delovoy Peterburg, hackers compromised a company DevOps engineer’s laptop. This gave them access to a service container and allowed them to initiate unauthorized transactions. About $3 billion of the stolen assets have already been frozen on the network. The FBI blamed the attack on North Korean hackers but has not yet presented public evidence, NUR.KZ notes.
Recovery stages
The first phase of resuming operations started on November 1. The exchange opened withdrawals for 15 crypto assets, including Bitcoin, Ethereum, Solana, USDT, and USDC. Priority went to tokens with the highest user demand over the past week.
By 3:00 PM Tashkent time on November 2, the platform enabled withdrawals in 28 traditional currencies. This list included US dollars, euros, as well as Kazakh tenge and Kyrgyz som. Finteqstan previously reported that Kazakhstan is building infrastructure for digital assets; withdrawals in tenge are now available to users again.
As of the morning of November 1, Binance had compensated clients for about 95% of the damage and fully restored balances for the ten most popular tokens.
Discrepancy in outflow estimates
After withdrawals opened, users began pulling out money, but estimates of the outflow scale differ.
According to Binance itself, in the first 9.5 hours, the exchange received withdrawal requests for $4.65 billion and accepted deposits of $1.01 billion. Net outflow stood at $3.64 billion—just over 2% of total assets on the platform.
Meanwhile, Reuters, citing the analytics platform DefiLlama, reported asset withdrawals of $5.8 billion. Binance representatives explained this difference by noting that DefiLlama’s algorithms do not account for funds the exchange transferred to its new “hot” crypto wallet.
Why it matters
The exchange is quelling panic using its own reserves: the company allocated over $6.34 billion from its corporate treasury and SAFU fund to fully cover user losses.
