SnifferCoin

Wallet custody, cryptographic trust boundaries, vulnerabilities, audits and practical defensive habits

Binance security chief explains why pausing withdrawals could not stop October 29 transfers

Pausing withdrawals does not necessarily stop funds from moving when an attacker has an existing on-chain authorization. In remarks reported on November 9, 2026, Binance chief security officer Jimmy Su said this was the obstacle Binance faced during an October 29 security incident.

Speaking in a Binance X Space fireside chat, Su said the authorization used by the attacker existed on-chain and did not pass through Binance’s withdrawal system. According to Su, stopping the transfers required a new on-chain transaction to revoke that authorization. He said Binance’s hot wallets use multi-party computation (MPC), so there was no single private key the team could use directly for revocation. The team had to devise a revocation process, 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 findings 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. Binance also planned to manage its internal AI tools and development environments to critical-infrastructure standards.