hack or exploit

A Decade Ago, a $6.3 Billion Hack Would Have Sunk Binance & BTC, Bitwise CIO Says

50Importance
no updates 6h+Status
8News media
12Pieces
Published
Updated
Since then
12 new reports
Also mentions
BTCBNBETH +2

Binance’s October 29 hot-wallet hack triggered withdrawals, reserve checks, and public statements from other exchanges and analysts. New reporting adds that the exchange later posted positive net inflows, that most impacted tokens were replenished, and that insurance may cover only a limited share of the losses.

Key claims & sources

✓
Matt Hougan of Bitwise said the Binance hack would have sunk the exchange a decade ago, while saying Bitcoin’s long-term direction was unchanged.
✓
Binance completed a zero-knowledge proof of reserves for ten major cryptocurrencies after the October 29 hack, letting users verify that their holdings were backed.
✓
Binance finished a cryptographic reserves snapshot dated October 31 and said at least ten major tokens were backed one to one, while saying the process was not a solvency audit.
✓
Binance posted $2.3 billion in 24-hour net inflows as withdrawals expanded after a day of heavy outflows.
✓
Crypto Briefing reported that Binance may recover little of the hack losses through insurance after the breach renewed attention on exchange security coverage.
✓
Binance recorded $5.28 billion in cumulative net outflows after withdrawals resumed, with customers moving $10.97 billion from the exchange over about 46 hours and withdrawals peaking at $936 million in net outflows in one hour.
✓
Binance said 98% of the impacted tokens had been replenished and said pausing withdrawals did not stop every outflow.
✓
Coinbase said the Binance hot-wallet hack had no effect on its systems or customer funds, and said more than 99% of its customer assets were held in cold storage.

What it means

Proof-of-reserves checks became an industry norm after FTX collapsed in November 2022 without warning, leaving customers unable to verify that deposits were backed. Binance, the largest exchange by volume, had already run periodic attestations before the October 29 hack, but this is the first time it has paired a zero-knowledge proof with a crisis of this scale, letting any of its users cryptographically check 1:1 backing for ten major tokens without exposing other customers' balances.

For Binance's roughly 335 million account holders, the practical change is that they can now self-verify holdings in BTC, ETH, BNB, SOL and XRP rather than take the exchange's word for it. Binance says 98% of impacted tokens have been replenished, and net flows swung from $5.28 billion in outflows to $2.3 billion in inflows as withdrawals resumed. Separate reporting suggests insurance may cover only a limited share of the $6.3 billion loss, meaning the exchange's own reserves carry most of the repair.

Binance itself was careful to call the snapshot a reserves check, not a solvency audit, and that distinction matters more than it sounds. A proof of reserves confirms assets exist at a point in time; it says nothing about liabilities, off-balance-sheet obligations, or whether the same funds could be double-counted across products. Treating cryptographic snapshots as a substitute for independent, liability-inclusive audits lets exchanges claim transparency while regulators and depositors still lack the fuller picture that traditional audited financial statements would provide. (per cryptopolitan.com)

Outside analysts reviewing the blockchain trail say they can see repeated drains from Binance's hot wallets but cannot determine from public records alone what internal signing controls or transaction limits were in place when the theft occurred. Whether Binance discloses or submits to independent review of those wallet-signing policies, rather than relying on after-the-fact reserve snapshots, will determine if this episode changes custody practices industry-wide or simply becomes another costly breach absorbed and moved past. (per cointelegraph.com)

Market reaction i

BNBBNB it is the asset of the company or protocol in the event
first headline
-0.2% 2 h before
+0.9% 4 h after
$698.11price at publication
12data points

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.

first
Nov 2 00:40
+13 h 9 m
Nov 2 13:48
crypto.news context
Its angle: cryptocurrencies, completed, allowing
+13 h 52 m
Nov 2 14:32
Crypto Briefing context
Its angle: transparency, verifying, enhances
+16 h 13 m
Nov 2 16:52
+20 h 35 m
Nov 2 21:15
CR Cryptopolitan context
Its angle: cryptographic, technologies, commitment; with quotes
+1 d 10 h
Nov 3 11:32
+1 d 12 h
Nov 3 12:44
Crypto Briefing echo
No new facts: comprehensive, vulnerability, insurance
+1 d 13 h
Nov 3 14:26
Crypto Economy adds
Breaks the figures down; the largest, $5.7B, with quotes
+1 d 14 h
Nov 3 14:43
The Defiant adds
Sharpens the figure: $6.3B, with quotes
+2 d 10 h
Nov 4 11:11
Cointelegraph context
Its angle: institutional, highlighted, grayscale
+2 d 14 h
Nov 4 15:18
crypto.news context
Its angle: reportedly, unaffected, according; with quotes
+4 d 10 h
Nov 6 10:40
Cointelegraph context
Its angle: transaction, blockchain, questions

Thefts of a similar size

WhenWhat happenedFigure
5.9 years ago LuBian · Weak key generation incident $3.5B
5.6 years ago Thodex · Scam incident $2.5B
5.4 years ago Africrypt · Scam incident $2.3B
6.4 years ago Wirecard · Scam incident $2.1B
5.2 years ago BitConnect · Scam incident $2B

4285 incidents stored · 0 were as large as this one or larger ($6.3B)