Jefe de seguridad de Binance: pausar los retiros no podría haber detenido el hackeo porque los atacantes tenían aprobaciones on-chain
En un X Space el 9 de noviembre, el CSO de Binance, Jimmy Su, dijo que las aprobaciones que usaron los atacantes estaban on-chain, fuera del sistema de retiros de Binance, y que revocarlas desde una hot wallet MPC sin una única clave privada tomó horas. Dijo que expertos externos revisarán el incidente de forma independiente y que Binance está estableciendo un fondo de investigación de seguridad sobre amenazas relacionadas con la IA.
Original: Binance security chief: pausing withdrawals could not stop the hack because the attackers held on-chain approvals Traducción IA
In a 9 November X Space, Binance CSO Jimmy Su said the approvals the attackers used sat on-chain, outside Binance's withdrawal system, and that revoking them from an MPC hot wallet with no single private key took hours. He said outside experts will independently review the incident and Binance is setting up a security research fund on AI-related threats.
Declarado por una persona, cuenta o publicación identificada; la fuente está enlazada abajo. Informamos lo que dice la fuente, no una conclusión propia.
Binance's chief security officer, Jimmy Su, gave the exchange's most detailed explanation so far of why the 29 October hot-wallet drain kept going after withdrawals were paused. According to PANews, ChainCatcher and TokenPost, he said in a fireside chat on a Binance X Space on 9 November that the transaction approvals the attackers used existed on-chain and did not pass through Binance's withdrawal system, so pausing withdrawals could not stop them; separate on-chain transactions were needed to revoke them.
Because the hot wallet uses multi-party computation (MPC), there was no single private key that could revoke the approvals at once, Su said, and the team had to devise a revocation process on the spot, which is why containment took several hours.
Su said Binance is hiring outside security experts for a full independent review to check its internal findings, is setting up a security research fund with AI companies and security firms focused on AI-related threats to blockchains, and will manage internal AI tools and development environments to critical-infrastructure standards. PANews also reports him saying the attack used zero-day malware that third-party endpoint protection did not detect at the time.
These statements come from media reports of the X Space; cz.wiki has not reviewed a recording or transcript. Binance's own earlier findings are summarised in the hack article.
Fuentes
- Binance CSO: Security Research Fund Being Established to Focus on AI-Related Security Threats in Blockchain — PANews, 2026-11-09
- 币安首席安全官:正筹建安全研究基金,重点研究区块链与 AI 相关安全威胁 — ChainCatcher, 2026-11-09
- Binance Explains Why Withdrawal Pause Failed to Stop Oct. 29 Transfers — TokenPost, 2026-11-10