Here's how big bitcoin traders responded after the Binance hack hit

Your day-ahead look for Oct. 30, 2026
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Your day-ahead look for Oct. 30, 2026
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Binance has set aside its own funds to cover losses from a crypto hack valued at about $6.3 billion, which the exchange describes as record-breaking. The company has also frozen roughly $3 billion of the stolen assets. The reserved funds are meant to make affected users whole, with the exchange drawing on its own capital rather than customer deposits. The article provides limited detail on the timing and method of the attack. The hack underscores the scale of recent security breaches across the cryptocurrency sector.

A bad actor exploited a 2025 Ethereum upgrade, which was designed to give standard wallets smarter functionality, to move assets out of Binance's holdings. The attacker reportedly used 50 signatures associated with Binance's own wallet to authorize the transfers. The episode is linked to part of a roughly $6 billion loss reported by the exchange. The article explains how the upgrade's features contributed to the drain. Further details on the scope and remediation were not specified in the source excerpt.

Bitcoin traded near $77,350 following a hack of Binance that reportedly involved $6.3 billion. The fallout drove crypto futures liquidations up to $1.57 billion. Bitcoin and ether both moved lower as traders reacted to the breach. The source article provides limited detail beyond these figures and price movements.

Strategy's chief financial officer, Andrew Kang, has stepped down from his role. The departure coincides with the company reporting $21 billion in quarterly operating income, a record for the firm. Strategy also disclosed that it holds 848,517 bitcoin on its balance sheet. Despite the strong earnings, the company's MSTR stock fell 6% following the news.

Discussion (0)
Log in to join the discussion and vote.
Log in