Is Binance Being Hacked? $2 Billion Outflow Puts Customer Funds in Question
- Published
- Updated
- Since then
- 119 new reports
- In
- Exchanges
Binance said a potential security incident moved about $6.3 billion from its hot wallets on October 29, and stablecoin issuers later froze large amounts tied to the flows. In the days after, Binance said it would cover losses, restored backing for most affected assets, and resumed withdrawals while investigators and blockchain firms kept tracing the remaining funds.
Key claims & sources
What it means
Binance's hot-wallet architecture has been a known weak point since Mt. Gox and the 2019 Binance hack that cost $40 million, but this breach dwarfs every prior exchange theft, including Bybit's $1.5 billion loss earlier in 2025. Investigators now describe a single compromised DevOps laptop, not a smart-contract flaw, opening the service container that signed withdrawal transactions across ten blockchains.
Traders who held BNB or kept balances on Binance watched withdrawals freeze for days while the exchange rebuilt reserves token by token; by November 1 users pulled $4.649 billion against $1.01 billion in deposits within hours of reopening. Rivals such as OKX picked up inflows as some depositors moved to self-custody or other venues, and borrowers on Aave found 292 reserves frozen mid-position after a hacker-linked wallet used stolen USDT as loan collateral.
Tether and Circle froze roughly $1.8 billion within hours, proof that stablecoin issuers, not courts, now act as the fastest circuit breaker in crypto when a hack this size hits. That speed is also the uncomfortable part: the same centralized blacklist that stopped the Binance hacker could just as easily be pointed at any other wallet, and depositors who think of USDT or USDC as bearer instruments are being shown otherwise in real time.
Binance's request to Arbitrum's DAO to release 8,425.997 ETH and 74.56 million ARB, filed November 5, starts a governance vote the exchange says could run seven weeks or longer, and will show whether a decentralized chain's token holders, not an exchange or an issuer, end up deciding what happens to frozen hack proceeds. A yes vote returns funds to Binance's reserve; a no, or a long stalemate, leaves Arbitrum holding assets tied to the largest theft in crypto history.
Market reaction i
The move was larger before the first headline than after. That is an observation, not an explanation: the market also moves on things nobody publishes.
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Thefts of a similar size
| When | What happened | Figure |
|---|---|---|
| 8 days ago | Binance CEX · Key Leaked via Infrastructure incident | $6.4B |
| 8 days ago | Binance · DevOps Engineer’s laptop compromised incident | $6.3B |
| 5.9 years ago | LuBian · Weak key generation incident | $3.5B |
| 5.5 years ago | Thodex · Scam incident | $2.5B |
| 5.4 years ago | Africrypt · Scam incident | $2.3B |
4280 incidents stored · 0 were as large as this one or larger ($171B)