Binance security chief explains why pausing withdrawals could not stop an on-chain authorization

In remarks reported on November 9, 2026, Binance chief security officer Jimmy Su said the company was hiring external security experts to independently review an October 29 security incident. Speaking during a Binance X Space fireside chat, Su said the review would check the findings of Binance’s internal investigation and recommend improvements.

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

According to Su, Binance’s hot wallets use 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, and that it took several hours to bring the situation under control.

Su also 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 planned to manage its internal AI tools and development environment according to critical-infrastructure standards. These were described as plans, not completed measures.

Further reading