Binance Security Chief Explains Why Pausing Withdrawals Did Not Stop On-Chain Transfers

For builders designing authorization and recovery workflows, a distinction matters: an on-chain transaction authorization is not controlled by an exchange’s withdrawal system. In a report published on November 9, 2026, Odaily described Binance chief security officer Jimmy Su’s explanation of an October 29 security incident during a Binance X Space conversation.

Su said the authorization used by the attacker existed on-chain and did not pass through Binance’s withdrawal system. Pausing withdrawals therefore could not stop the related transfers; revoking the authorization required a new on-chain transaction.

According to Su, Binance’s hot wallet uses multi-party computation (MPC), so there was no single private key that could be used directly to revoke the authorization. He said the team had to devise a revocation process at the time, and it took several hours to bring the situation under control.

Su also said Binance was hiring external security experts to independently review the incident, check its internal investigation’s conclusions and recommend improvements. Separately, he said Binance was working with partners, including leading AI and security companies, to establish a security research fund focused on AI-related threats in blockchain. He described managing internal AI tools and development environments to critical-infrastructure standards as a future plan, not a measure already in place.

Further reading