A withdrawal pause would not have stopped the transfers linked to Binance’s October 29 security incident, according to the company’s chief security officer, Jimmy Su. In remarks reported on November 9, 2026, Su said the attacker used a transaction authorization that existed on-chain, outside Binance’s withdrawal system. Stopping the transfers required a new on-chain transaction to revoke that authorization.
Su said the response took several hours because Binance’s hot wallet uses multi-party computation (MPC), rather than a single private key that could be used directly to revoke the authorization. The team had to devise a revocation process before it brought the situation under control, he said.
Binance was hiring external security experts to independently review the incident, check its internal investigation and recommend improvements, Su said. He also said the company was working with AI and security partners to establish a research fund focused on AI-related security threats in blockchain. Separately, Binance planned to manage its internal AI tools and development environments according to critical-infrastructure standards. These were plans described by Su, not measures reported as complete.