OfficialresponseStatement 1739
We are engaging independent third-party cybersecurity experts to conduct a comprehensive review of the incident, validate our findings and recommend additional measures.
Binance said it is engaging independent third-party cybersecurity experts to conduct a comprehensive review of the incident, validate its findings and recommend additional measures.
This line is our short summary of the quote below. The quote is the evidence.
From this source: 29 October 2026 Binance Security Incident: Initial Findings and Response Update (Binance Blog, archived copy captured 2026-11-05), with all of its statements.
Other statements from the same source
OfficialresponseStatement 1740
Binance said it is working on establishing a security research fund and targeted initiatives with AI companies, industry participants and security firms focused on AI security in blockchain environments.
We are working on establishing a security research fund and targeted initiatives with leading AI companies, industry participants and security firms focused on AI security in blockchain environments.
OfficialresponseStatement 1738
Binance said that as of 3 November it had rebuilt the affected wallet system in a new environment, rebuilt the affected internal AI tool and access controls, replaced affected devices and decommissioned credentials and tokens related to the affected engineers.
As of Nov 3, 2026, we have taken the following actions: * Rebuilt the affected wallet system in a new environment. * Rebuilt the affected internal AI tool and access controls. * Replaced affected devices. * Decommissioned credentials and tokens related to affected engineers.
OfficialresponseStatement 1737
Binance said it received an internal alert regarding large-volume transfers and immediately began investigating.
Binance then received an internal alert regarding large-volume transfers and immediately began investigating.
OfficialresponseStatement 1736
Binance said that because the hot wallet used Multi-Party Computation (MPC), there was no single private key that could be used to immediately revoke the malicious EIP-7702 authorizations, so its team developed and executed a specialized revocation procedure, which required additional time.
Because the hot wallet used Multi-Party Computation (MPC), there was no single private key that could be used to immediately revoke the malicious EIP-7702 authorizations. The team therefore developed and executed a specialized procedure to revoke these authorizations, which required additional time.
Officialroot causeStatement 1735
Binance said suspending withdrawals alone could not stop all unauthorized asset movements, as the malicious EIP-7702 authorizations existed on-chain and operated independently of its normal withdrawal infrastructure, and that the attackers submitted 50 signing transactions to manipulate the account nonce and establish malicious delegation authorizations.
However, suspending withdrawals alone could not stop all unauthorized asset movements. The malicious EIP-7702 authorizations existed on-chain and operated independently of Binance’s normal withdrawal infrastructure.The attackers submitted 50 signing transactions to manipulate the account nonce and establish malicious delegation authorizations.