Credit where it is due
Binance covered the loss, said that 98% of impacted token assets had been replenished by 31 October, and published a detailed account of how the attack worked so that others can learn from it (Binance initial findings). Few firms publish that much that quickly. This paper is written in the same spirit. It is not a claim about what any team should have known. Facts are cited to public sources. The analysis is ours.
The FBI has attributed the theft to North Korea, under the activity name TraderTraitor (FBI alert). This was a patient, well-resourced operation. The lesson is not that someone made a simple mistake. The lesson is about where the last check sits.
What the public record says
- June 2026A tampered install. A wallet DevOps engineer downloaded a tampered Homebrew installation while trying to install an AI coding tool. The device was replaced and credentials rotated, but the team was now known to the attacker (Binance).
- SeptemberA fake job interview. A second engineer was approached on a legitimate hiring platform, interviewed twice, and asked to run an "assignment" repository on his work computer. The malware swapped a developer tool component, was not caught by endpoint protection, and removed its own traces (Binance).
- 20 OctoberAn internal AI tool as a springboard. From that computer, the attacker used an internal AI tool to reach two more engineers and found a container deployment token on one of their machines (Binance).
- 29 Oct, 17:15 to 19:56 UTCOne engineer's credentials, another engineer's computer. The attacker logged onto one engineer's computer with credentials stolen from another, deployed a container and started a script that reached the wallet signing service (Binance).
- 20:05 UTCThe outflow. Five hot wallets sent 233.46 million XRP in four minutes. Across ten chains, most of about USD 6.36 billion moved in roughly twenty minutes (BleepingComputer).
- Same eveningStanding authority. Fifty signing transactions moved an account nonce and set up EIP-7702 delegations. Those authorisations lived on chain, so pausing withdrawals did not cancel them. Because the wallet used MPC there was no single key to revoke them at once (Binance).
- 23:56 UTCThe last transfer. 2,961.9 ETH, broadcast earlier, finalised on chain.
- 30 Oct, 00:10 UTCDelegation cleared. A new authorisation to the zero address cleared the delegation code (Binance).
Four places the signer had no reason to say no
The signer trusted the caller
Binance writes that the attacker used the signing service to "initiate transactions outside the normal withdrawal process." Whatever approvals the withdrawal process held, the signer did not ask to see them.
Credentials travelled
A token issued to one engineer worked from another engineer's computer. Nothing tied the credential to the person and device it was issued to.
Authority outlived the stop button
The delegations were themselves signed like ordinary transactions. Once on chain they kept working after withdrawals were paused, and revoking them took a custom procedure.
Evidence sat with the attacker
The malware removed traces on the machines it touched. When the record lives where the attacker is, the investigation starts behind.
The principle
A valid credential should never be the only thing a signer needs.
Before a signer signs, it should require a short signed slip, an approval receipt, issued by a separate system that the requester does not control. No slip, no signature. The slip is narrow on purpose.
The worst case is the balance of the hot wallet.
The worst case is the allowance you chose in advance.
Six rules
- Bind the approval to one exact transaction. Destination, asset, amount, chain and nonce are inside the slip. A slip for one transfer cannot sign another, and it expires in minutes.
- Spend from an allowance the signer enforces. Each hot wallet has a limit per window. The signer counts down that limit itself and stops at zero, whoever is asking.
- Treat authority changes as the most sensitive action. A delegation, a contract approval or a signer policy change is not a withdrawal. It needs a higher quorum, a delay, an expiry, and a revocation that is already signed and waiting.
- Bind credentials to who they were issued to. A token used from a different person's device or session is refused, and the refusal is recorded.
- Write to an outside witness as things happen. Requests, approvals, refusals and signatures leave the building in real time. A refused request is evidence too.
- Make the stop button reach standing authority. One action should pause new signing, set allowances to zero and push the pre-signed revocations.
Would it have changed this incident?
Honestly, in part. Receipts do not stop a fake job interview or zero-day malware. They change what a foothold is worth.
| Step in the attack | What a signing-path receipt changes |
|---|---|
| Laptops compromised | Nothing. This is outside the signing path. |
| One engineer's token used from another's computer | Refused or flagged if credentials are bound to the person and device. |
| Transactions sent outside the withdrawal process | The signer asks for an approval slip, finds none, refuses, and records the refusal. |
| Fifty delegation signatures | Each is an authority change. Each waits for a higher quorum and a delay. Fifty in minutes trips the line. |
| Withdrawals paused, delegations still live | The stop button zeroes allowances and pushes pre-signed revocations. |
| Traces removed | The outside witness still holds every request and refusal. |
What it would not fix. If one attacker controls both the approval issuer and the signer, nothing here helps. The design depends on separation, and separation has to be real: different systems, different people, different credentials. We also do not know Binance's internal controls beyond what it has published. It says it has strengthened wallet service risk controls and is reviewing signing policy coverage and hot wallet controls (Binance).
The question to answer in advance
Every exchange and custodian can answer one question before the next incident: how much are we willing to lose in the worst twenty minutes? Without an allowance at the signer, the answer is set by whatever the hot wallet holds. With one, it is a number someone chose on a calm day. That number is the product.
A checklist for exchanges and custodians
- Can your signer sign anything without an approval issued by a different system?
- Is each approval bound to one exact transaction, and does it expire?
- Who sets the allowance for each hot wallet, and does the signer itself enforce it?
- Do delegations, contract approvals and signer policy changes need more than an ordinary withdrawal?
- Does your stop button revoke standing authority, or only pause new withdrawals?
- Can a credential issued to one engineer be used from another engineer's machine?
- Where do your signing records live, and could the attacker who reached your signer delete them?
- Could you show an independent party, within an hour, every request your signer received and which ones it refused?
Where Hive fits
Hive issues signed receipts at the moment of action and keeps them where the actor cannot rewrite them. The pieces this paper relies on are already public:
