Binance security incident highlights wallet-signing and authorization risks

For wallet builders, the October 29, 2026 Binance security incident raises two questions: who can access an internal signing service, and how can an on-chain authorization be revoked if a wallet has no single private key?

According to a report published on November 5, 2026, attackers used a fake job interview, a malicious code repository, a compromised internal AI tool and endpoint infiltration to gain access to the wallet team. The report says they then used an internal wallet-signing service and Ethereum’s EIP-7702 authorization mechanism to transfer assets. It puts the digital assets affected at approximately $6.34 billion; that figure is not stated as the amount transferred.

Binance suspended withdrawals and froze approximately $2.85 billion in assets. The report says revoking the on-chain authorization required a dedicated process because the MPC wallet had no single private key. It also describes an attack-preparation timeline, a reported North Korea connection, response measures and a subsequent independent security review. The brief account does not establish the details of that connection or the review’s outcome.

Source: learnblockchain.cn (originally published 2026-11-05 00:04 UTC+8)

Further reading