Binance hack timeline: from suspicious transfers to a $6.34 billion reserve

Binance hack timeline: from suspicious transfers to a $6.34 billion reserve

All times are UTC. Information as of October 30, 2026.

On the evening of October 29, analysts noticed unusual transfers from Binance’s hot wallets. The first reports concerned movements of more than $2 billion in assets, while the circumstances remained unclear. Statements from Changpeng Zhao, the exchange itself and stablecoin issuers followed. By October 30, Binance had estimated the incident’s impact at approximately $6.3 billion, reported that some funds had been frozen and announced that it was setting aside its own reserves to cover the losses.

The beginning of the attack was reconstructed later from blockchain transactions. According to TRM Labs’ investigation, funds began leaving Binance wallets on the XRP Ledger at around 20:05 on October 29. Over the following minutes, suspicious transfers affected other networks. At approximately 20:20, 18,270 BTC left the exchange’s Bitcoin wallet, while large movements were also taking place on TRON and Ethereum. TRM Labs’ reconstruction.

At 20:24, one of the largest transfers took place: 167,464 ETH, approximately 1.6 billion USDT and other tokens left the wallet labelled Binance 14. According to Bitquery’s reconstruction, a series of EIP-7702 authorizations had been used on Ethereum shortly beforehand, allowing the wallet to execute code from an attacker-controlled smart contract. These transactions later became an important part of the technical analysis of the incident. Bitquery’s investigation.

At around 20:32, analyst Spreek posted one of the early public warnings. He drew attention to a potentially large-scale incident and the transfer of a wallet’s contents to a new address. At that stage, the hack remained unconfirmed. Spreek’s post.

The first reports cited figures exceeding $2 billion and $2.5 billion. Analysts discussed a possible compromise of access, but still allowed for the possibility of a routine transfer between the exchange’s wallets. A Binance representative told BeInCrypto that the company was aware of a potential security issue and was conducting checks. There was no confirmation at that point that user funds had been affected. NV’s early report.

While the public picture was still emerging, assets linked to the attack were already moving through other services. Between 20:58 and 21:01, one address supplied approximately 60 million USDT to the Aave lending protocol and borrowed 19,762 WETH. Some of the stablecoins were therefore used as collateral to obtain a different asset. The risk management team at LlamaRisk later described these transactions. LlamaRisk’s report.

At 21:01, Tether froze the main recipient address, which held approximately 971.1 million USDT. At 21:04, Circle froze approximately 823 million USDC. These were the first major confirmed measures to restrict the movement of funds. According to TRM Labs, the attacker was simultaneously trying to convert stablecoins into other cryptoassets ahead of further freezes. TRM Labs’ findings.

At around 21:15, Binance founder Changpeng Zhao publicly stated that the events looked like a hack. He thanked Tether and Circle for quickly freezing funds and said he expected all user funds to be fully covered. Zhao specifically noted that he no longer managed Binance, so his message reflected the position of the company’s founder and shareholder. CZ’s post.

Binance’s initial messages referred to an investigation into a potential incident. The exchange reassured users that their funds were safe and promised to publish verified information through official channels. A detailed explanation of the attack mechanism and a final assessment of its scale were not yet available. Binance’s initial statement.

At 21:25, Tether CEO Paolo Ardoino reported that more than 1.567 billion USDT linked to the suspected Binance hack had been frozen. This exceeded the initial figure of approximately $971 million: additional assets were being blocked as transfers were traced. The figures emerging throughout the evening therefore reflected different stages of the response. Paolo Ardoino’s statement.

Between 21:42 and 23:04, Aave introduced restrictions on opening new supply and borrowing positions across a number of markets. The protocol sought to limit further use of the stolen assets. Loan repayments, withdrawals and liquidations remained available. LlamaRisk said the attacker’s identified position was overcollateralized and did not pose a risk to Aave depositors at the time of the report. Aave’s response explained.

Late in the evening, Binance reported withdrawal restrictions and linked their restoration to the completion of security checks. An update to that effect was published at 22:33. The posting time should not be treated as the exact minute when operations were actually halted. Binance’s update.

Overnight into October 30, the Arbitrum Security Council joined the response. It reported moving approximately 74.56 million ARB and 8,425 ETH linked to the attack into an interim frozen wallet. Binance, meanwhile, continued to update the overall figure for blocked assets: by 00:52 on October 30, the company reported approximately $3 billion. Arbitrum’s statement, Binance’s update on frozen assets.

At 02:25, Binance published its first detailed findings. The exchange estimated the incident’s impact at approximately $6.3 billion. Its preliminary investigation pointed to a compromised DevOps engineer’s laptop: the attacker may have used it to access a service container and initiate unauthorized withdrawals. The company said it had found no evidence of wallet private key leaks and committed to covering losses through the SAFU fund and its own resources. Binance’s statement.

The early reports of suspicious transfers had now been followed by an official assessment of their scale. The initial figures of approximately $2 billion described only part of the observed transactions. The $6.3 billion figure remained an estimate of affected assets, while the final irrecoverable loss depended on fund recovery and the investigation’s findings.

At 04:36, Binance clarified the status of its services: deposits were operating normally, while withdrawals remained paused as the team upgraded the security of the service and its associated addresses. The company expected withdrawals to resume within 48 hours of that message. This was an estimate; the exact time for restoring operations was to be announced separately. Binance’s service update.

By the morning of October 30, the market impact was also visible. According to Reuters, as reported by DW, Bitcoin fell as low as $76,368 during Asian trading, while Ethereum reached $2,178. Both assets declined by more than 3%. These figures relate to a particular point in the trading session and are not current prices. DW’s report.

Analysts also raised the possibility of involvement by the North Korean group TraderTraitor. TRM Labs linked the attack to the group on the basis of its own intelligence and estimated the funds withdrawn at approximately $6.36 billion. At this stage, attribution to the group was the analytical company’s conclusion. TRM Labs’ investigation.

In its next detailed update, published at around 08:47, Binance refined its preliminary account of the intrusion. The investigation had identified additional entry points, and the attack proved to involve multiple stages. The company emphasized that the incident could not be reduced to a single device or the actions of one engineer. The absence of detected evidence of private key leaks remained the exchange’s position; the technical report was still being prepared. Binance’s clarification of the attack mechanism.

Later on October 30, Binance announced that it had begun restoring affected user assets and said it had reserved more than $6.34 billion of company funds to cover the incident’s consequences. According to the exchange, $5 billion was already held in the corresponding tokens. The company was acquiring the remainder through market and over-the-counter transactions, or OTC. Binance’s reserve announcement.

The exchange warned that restoring some positions could take longer because certain tokens had low liquidity and OTC trades required time to settle. Approximately $3 billion in frozen assets was being accounted for separately from the allocated reserve and remained subject to recovery and verification. Binance intends to verify the backing of user funds through its Proof of Reserves system.

At this stage, several possible market scenarios emerged. Sales of stolen tokens could add pressure to prices, while Binance’s replenishment purchases could support demand for individual assets. If many customers decide to move their funds at once after withdrawals reopen, the exchange will need to meet increased liquidity requirements. The direction and scale of these effects have yet to be established.

For exchange services, potential delays depend on whether Binance is used in particular settlements and liquidity routes. Additional time may also be needed to check incoming funds. The attack alone does not establish anything about the condition of other companies’ reserves or operations.

As of the latest update reviewed, Binance had announced the allocation of funds and the start of asset restoration. Completion of that process, the reopening of withdrawals and the recovery of frozen cryptocurrency each require separate confirmation. The next practical stage will be the execution of customer requests once withdrawals reopen; the technical report should explain how the attacker gained access to the exchange’s infrastructure.