Binance called it a 'security issue.' On-chain data called it $5.7 billion.
Binance, the world's largest crypto exchange, halted withdrawals on October 29 after suspicious outflows drained an estimated $5.57 billion across three blockchains. The company's public statement said funds are 'completely safe' and called it a 'potential security issue.' Tether and Circle froze $1.79 billion in stablecoins in response. The gap between Binance's language and the on-chain numbers is the story. When the exchange is simultaneously pausing withdrawals and telling users everything is fine, one of those things is doing more work than the other.
Binance halts withdrawals amid suspected multi-billion dollar hack; Circle and Tether freeze affected funds
6 sources · hover a dot to see coverage
What happened
On October 29, 2026, Binance suspended withdrawals after on-chain analysts detected large outflows from the exchange's hot wallets. Decrypt tallied the drain at $5.57 billion across three blockchains. CoinDesk put the figure at $5.7 billion, calling it the largest crypto hack to date. The Block reported that Tether froze USDT and Circle froze USDC, together totaling $1.79 billion in frozen stablecoins. Bitcoin fell to $79,000 on the news. Binance's public statement described the event as a 'potential security issue,' said its teams were reviewing information 'with urgency,' and maintained that user funds are 'completely safe.' Etherscan records cited by Decrypt showed wallets linked to the suspected hack swapping freezable stablecoins for Ethereum on decentralized exchanges, suggesting the attacker was already trying to move funds beyond the reach of issuers. Seven outlets covered the story. What separates them is how much of Binance's own language they let stand unchallenged.
Crypto-native outlets put numbers on the drain; others quoted Binance's reassurance
Decrypt and The Block did the most specific work. Decrypt's on-chain tally named $5.57 billion across three blockchains and separately reported that the attacker was already swapping USDT and USDC for Ethereum on decentralized exchanges, a detail that matters because Ethereum cannot be frozen by an issuer. The Block specified that Tether and Circle froze $1.79 billion combined. CoinDesk added market context: bitcoin at $79,000. CNBC and Forbes both quoted Binance's 'completely safe' language prominently, with Forbes' headline built around it. Neither outlet put the on-chain dollar figure in its headline. The Block's headline read 'suspicious outflows reach up to $5.8 billion.' Forbes' read 'User Funds Are Completely Safe.' Those are not the same story.
The attacker's exit strategy appeared in one outlet and nowhere else
Decrypt's second piece, headlined 'Binance Hacker Hunts for Exit Ramps as DeFi Exchanges Pause Markets,' reported a specific and consequential detail: the suspected attacker was using decentralized exchanges to swap freezable stablecoins into Ethereum. Etherscan records were cited. This matters because Circle and Tether's freeze only works on assets they control. Once funds convert to Ethereum, that lever is gone. No other outlet in this group reported on the attacker's post-hack behavior. CNBC, Forbes, and TechCrunch covered the freeze as the response. Decrypt covered whether the response was working.
What one side told you that the other didn't
Binance said 'completely safe.' The attacker had already moved $5.7 billion.
Forbes built its headline around Binance's 'completely safe' claim. CNBC's headline named the freeze but quoted the same language in the lede. Neither headline contained a dollar figure. Decrypt's headline named $5.57 billion. The Block named $5.8 billion. CoinDesk named $5.7 billion and called it the largest crypto hack to date. A reader who saw only the Forbes or CNBC headline would know there was a 'security issue' and that funds are reportedly safe. A reader who saw the Decrypt or CoinDesk headline would know the scale of what moved before anyone froze anything.
The freeze is only as good as the assets it can reach.
The $1.79 billion frozen by Tether and Circle is the detail every outlet covered. The detail only Decrypt covered is that the attacker was already converting those freezable assets into Ethereum, which neither issuer can touch. That conversion, visible on Etherscan, is the difference between a response that works and one that arrives too late. Six outlets reported the freeze. One reported whether it mattered.
Nobody named which three blockchains lost the $5.57 billion.
Decrypt's on-chain tally specified that the drain spread across three blockchains, but did not name them in the excerpt. No other outlet in this group specified which chains were affected. That omission is not trivial: the answer determines which assets are recoverable, which bridges or protocols were exploited, and how the attacker moved funds at that scale. The largest crypto hack on record, and the attack surface is still unspecified in every piece of coverage available here.
TechCrunch's excerpt is just its own headline, repeated.
TechCrunch's entry in this group contains no reporting. The excerpt field reads: 'Binance pauses withdrawals as hackers suspected of stealing billions in crypto — TechCrunch.' That is the headline, verbatim, with the outlet name appended. No dollar figure, no named source, no detail not already in the headline. For a story of this scale, from an outlet with a full tech and crypto desk, the absence of any substantive excerpt is its own data point about where editorial bandwidth went on October 29.
What to watch
Binance has not confirmed a specific dollar figure or named the exploit vector as of October 29. If the company issues a formal post-mortem within 72 hours, watch whether the confirmed loss figure matches the $5.57–5.7 billion on-chain estimates or comes in materially lower. A significantly lower official figure would likely prompt CNBC and Forbes to revisit their 'completely safe' framing. If no post-mortem appears by November 1, the absence itself becomes the story, and crypto-native outlets will cover it; mainstream outlets probably won't.
See how outlets across the political spectrum framed this differently — and what each side left out.