FBI attributes $6B Binance theft to North Korea’s TraderTraitor
The FBI named North Korea’s TraderTraitor in Binance’s $6.34 billion theft; EIP-7702 authorizations let attackers keep moving funds after withdrawals stopped.
The Finality Desk3 min read#878040

The FBI attributed the theft of more than $6 billion in virtual assets from Binance to North Korea’s TraderTraitor, and urged crypto firms to block addresses linked to the laundering. The FBI’s October 31 alert says the theft occurred on or about October 29. It identifies the group and describes how investigators have tracked the proceeds, but does not detail the breach path.
Binance’s November 3 incident update puts the impact at approximately $6.34 billion. The exchange says attackers used unauthorized access to its internal wallet signing service to initiate transactions outside the normal withdrawal process. The FBI says it has observed the stolen assets being converted primarily into Ether, with further laundering expected through decentralized finance and instant swap services.
How did the attackers move funds from Binance wallets?
Binance says the attacker used Ethereum’s EIP-7702 authorization mechanism to give a smart contract controlled by the attacker partial execution rights over a hot wallet. EIP-7702 allows an account to delegate certain execution rights to a contract without exposing its private key. The exchange’s incident update says the attacker accessed an internal wallet signing service and used that path to establish the on-chain permissions.
The outflows crossed several networks. Binance reports that five hot wallets sent 233.46 million XRP to an attacker-controlled address between 20:05 and 20:09 UTC. Hot wallets on Solana and Optimism sent approximately 970,500 SOL and 44.2 million OP. A Binance hot wallet also sent 18,270 BTC. The exchange says the final unauthorized transfer, 2,961.9 ETH, finalized on-chain at 23:56 UTC after being broadcast earlier and remaining pending.
Binance’s update says the attackers submitted 50 signing transactions to manipulate the account nonce and establish malicious delegation authorizations. That detail matters because the theft was not just a sequence of ordinary withdrawals: the on-chain permissions gave the attacker a way to execute transfers through a smart contract.
Why did pausing withdrawals not stop the outflows?
Binance says suspending withdrawals could not by itself revoke authorizations already recorded on-chain. Those permissions operated independently of the exchange’s normal withdrawal infrastructure, so closing that route did not remove the contract’s execution rights. Binance says it had to send additional transactions to revoke them.
The exchange also says its hot wallet used multi-party computation, or MPC, so no single private key existed to revoke the malicious permissions immediately. It developed a specialized procedure to remove the authorizations. At 00:10 UTC on October 30, Binance sent a new authorization from its Binance14 hot wallet to the zero address, clearing the EIP-7702 delegation code. Binance reports that no further unauthorized transfers occurred after the final transfer finalized.
What can other crypto firms do with the FBI’s attribution?
The FBI, together with the U.S. Secret Service and IRS Criminal Investigation, urged THORNode and RPC node operators, instant exchanges, DeFi services, analytics firms and other virtual asset providers to block transactions with or derived from addresses used by TraderTraitor. The alert says investigators expect the assets to pass through DeFi and instant swap services as the group prepares them for further laundering.
Binance says approximately $2.85 billion in assets had been frozen or intercepted as of its November 3 update, subject to reconciliation and market-price changes. It also said 98% of impacted token assets had been replenished as of October 31, with the remaining illiquid assets still being purchased. The investigation remains ongoing, and Binance said independent security firms would review its findings.
Sources and documents
- FBI’s October 31 alert — fbi.gov
- exchange’s incident update — binance.com