What Happened at Binance?
On October 29, 2026, Binance experienced a major security incident involving unauthorized withdrawals from its hot wallets. The estimated financial impact was about $6.3 billion, involving multiple crypto-assets across several blockchain networks.
Binance’s initial investigation suggested that the attack may have originated from a compromised laptop belonging to an engineer. The attacker apparently used access obtained through that device to reach an internal service container, enabling them to submit unauthorized withdrawal instructions.
One detail is particularly revealing: Binance reported that it had found no evidence that wallet private keys had been leaked. This raises an important possibility. The attackers may not have needed to steal the private keys themselves. Instead, they appear to have compromised the systems and authorizations through which legitimate transactions could be approved and executed.
Blockchain investigators have identified the use of Ethereum’s EIP-7702 function as part of the attack. This function allows an externally owned account to delegate certain execution capabilities to smart contract code. Investigators reported that the attacker used pre-signed authorizations to redirect the behavior of an affected Binance hot wallet toward malicious code. The reported preparation of approximately 50 signed authorizations is especially interesting. By preparing authorizations covering different transaction nonce values, the attacker increased the likelihood that one would be valid when the attack was executed.
In other words, the weakness may not have been the cryptographic protection of the private key, but the integrity of the systems and processes authorized to act on behalf of the wallet. It is important to distinguish what has been established from what remains under investigation. Binance has not yet published a complete technical post-mortem, and the precise sequence of compromise remains subject to investigation.
The response has also demonstrated the importance of industry coordination. Binance has worked with blockchain intelligence firms, law enforcement and asset issuers to trace and freeze affected assets. Stablecoin issuers, including Tether and Circle, have taken action to freeze certain assets associated with the incident. Binance has also committed to absorbing the financial impact rather than passing the losses to customers.
The incident is therefore not simply a story about a vulnerability in a wallet. It is a story about access management, internal controls, transaction authorization, third-party dependencies and the ability of the wider ecosystem to respond when those controls fail.
The Regulatory Question: Where Does Custody Really Begin and End?
For regulators, one of the most important implications is that safeguarding cannot be assessed by looking at private key management in isolation. A firm might demonstrate it uses cold storage, multi-signature arrangements, hardware security modules, geographic separation and stringent key-management procedures. These are all relevant safeguards. But what happens if an attacker can compromise an employee’s laptop, access an internal application, manipulate a transaction-signing service or exploit an existing authorization? The private key may remain technically secure, but the assets can still be exposed.
This is precisely why regulators need to understand the full chain of control over customer assets.
The FCA’s new crypto-asset framework provides an important regulatory context. Its approach to safeguarding recognizes that control is not necessarily limited to physically holding a private key. The ability to bring about the transfer of the benefit of a crypto-asset can arise through different arrangements, including the operation of systems and the appointment of third parties.
This is particularly relevant to firms whose operating models rely on external custodians, wallet infrastructure providers, technology platforms or outsourced transaction-signing arrangements. The regulatory assessment should therefore extend beyond the question of who holds the key. It should consider who can initiate, approve, authorize, override or execute a transaction and what controls exist at each stage.