A withdrawal pause did not stop the fund transfers linked to Binance’s October 29, 2026 security incident, according to the exchange’s chief security officer, Jimmy Su. Speaking in a Binance X Space discussion, Su said the attacker exploited 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 Binance’s hot wallet uses multi-party computation (MPC), so there was no single private key the team could use directly to revoke the authorization. The team had to devise a revocation process, which he said took several hours before it brought the situation under control. His account is an explanation of the response, not a finding from an independent review.
As reported on November 9, 2026, Su said Binance was hiring external security experts to independently review the incident, verify its internal investigation and recommend improvements. He also said Binance was working with partners, including leading AI and security companies, to establish a research fund focused on AI-related blockchain security threats. Binance planned to manage its internal AI tools and development environment according to critical-infrastructure standards in the future. These were stated plans, not completed measures.