Protocols desk

The Spec Said No.

At 20:20 UTC on October 29, a transaction carrying fifty authorizations from an Ethereum wallet upgrade called EIP‑7702 hit the wallet labeled Binance 14. Forty‑nine of them had bounced off a stale counter like a key jammed into the wrong lock. The spec warned them never to build the interface that let this one through.

The headlines called it “the Binance hack.” That framing buries the actual story. Ethereum activated EIP‑7702 in May 2025. The upgrade lets any ordinary wallet borrow smart‑contract abilities by signing a short authorization. Think of it as handing a visitor a copy of your house key that also opens every future delivery left at your door. Useful if you trust the visitor. Catastrophic if you don’t. Once that authorization is accepted, the borrowed code runs as if the wallet itself wrote it.

Ethereum’s specification for the feature is blunt. Borrowed code gets “unrestricted access to the account.” So the spec drew a hard line: wallets should never offer a signing interface for these authorizations. The exact words: “There is no safe way to provide this interface.” MetaMask, the most widely used Ethereum wallet, listened and restricted delegation to its own audited contract. Binance’s hot wallet infrastructure did not restrict it at all. Who at Binance signed off on the design? The exchange has not said.

Read the spec, not the headline

So why did only one authorization out of fifty succeed? Each one needs to match the wallet’s current transaction counter, known as its nonce. TraderTraitor, the North Korean hacking group the FBI later attributed, fired authorizations at Binance 14 the way a burglar tests every key on a stolen ring. Most landed on stale counters. One caught the live number. That single match handed the attacker’s code the keys to a wallet routing billions in customer deposits.

50 authorizations fired at Binance 14 ■ one matched the live nonce  ·  49 bounced off stale counters

The sweeper ran for nearly four hours. Binance’s own deposit systems kept funneling fresh customer funds into Binance 14 while the malicious delegation was live. The attacker drained the wallet, watched the pipeline refill it, and drained it again. The horror is not just the breach. It is that the exchange’s plumbing worked against itself, pumping assets directly into the drain. Total outflow: $2.5 billion.

The manual nobody read

Our read: this is a structural pattern. In 2014, Mt. Gox, the exchange handling 70% of all Bitcoin volume, collapsed because its systems failed to account for transaction malleability. That is a documented protocol behavior that let attackers alter transaction IDs to trick the exchange into re‑issuing withdrawals. The flaw sat in the open like an unlocked gate on a bank vault. Mt. Gox never built defenses against it. Binance repeated the pattern at a vastly larger scale. Same mechanism: a documented warning, an unbuilt defense, and an attacker who read the manual the exchange did not.

The exposure is not past tense

The number that should keep you awake: 63% of all EIP‑7702 authorizations observed across seven chains through mid‑2025 were tied to malicious contracts. Mingyuan Huang and colleagues published that figure in a peer‑reviewed study at USENIX Security ’26. That is the field’s top academic cybersecurity conference. This was not an isolated exploit. The feature was weaponized from its first month, turned into an industrial‑scale pump draining wallets across the ecosystem.

EIP‑7702 authorizations tied to malicious contracts 63% across seven chains through mid‑2025 · USENIX Security ’26

The same study flagged $10.14 million in potential exposure in old contracts that assumed externally owned accounts could not execute code. Those wallets are not exchanges with billion‑dollar war chests. They belong to individuals who approved a signing prompt that landed on their screens like any routine confirmation box. The spec said that box should never exist.

The thirty‑fifth authorization hit Binance 14 because the exchange built what the spec told them not to build. The fifty‑first wallet with a live malicious delegation will not have $6.3 billion in reserves behind it. Crypto Compass holds no position in BNB or tokens referenced in this piece.