Binance Security Chief Explains Why Pausing Withdrawals Could Not Stop October 29 Transfers

To stop the funds moving after Binance’s October 29 security incident, its team needed to revoke an on-chain transaction authorization—not simply pause withdrawals, according to chief security officer Jimmy Su.

In remarks reported on November 9, 2026, Su said during a Binance X Space fireside chat that the authorization used by the attacker existed on-chain and did not pass through Binance’s withdrawal system. Revoking it required a new on-chain transaction. He said the process took several hours because Binance’s hot wallet uses multi-party computation (MPC), leaving no single private key the team could use directly to revoke the authorization. The team had to devise a revocation process before it brought the situation under control, he said.

Su also said Binance was hiring external security experts to conduct a comprehensive independent review of the incident, check its internal findings and recommend improvements. Separately, he said Binance was working with partners, including leading AI companies and security firms, to establish a security research fund focused on AI-related threats in blockchain. He said Binance also planned to manage its internal AI tools and development environments according to critical-infrastructure standards. These were plans described by Su, not completed measures established by the report.