Morning Edition · Friday, November 6, 2026Published at 4:52 AM EST · New York
The FBI blames the TraderTraitor unit for the $6.3 billion theft, and in the same week Mercado Bitcoin customer deposit addresses kept draining for four hours after the Brazilian exchange said its own breach was contained.

Binance published its first incident report on November 3. It says the theft of about $6.3 billion began with a fake recruitment process. According to BleepingComputer, the attackers gave an engineer a malicious coding assignment and took control of the engineer's work computer. From that machine, with the help of an internal artificial-intelligence (AI) tool, they compromised two engineers on the wallet infrastructure team and took their credentials and a container deployment token. On October 29 they used those credentials to deploy a malicious script that reached the exchange's wallet signing service.
SecurityWeek reports that the attackers also used the signing service to abuse an Ethereum Improvement Proposal (EIP) feature, EIP-7702, which lets an ordinary account hand execution to a smart contract. This gave a contract the attackers controlled partial execution rights over a hot wallet. No contract had a bug. The attack vector was social engineering, followed by a compromise of the systems that hold signing authority. The signing service then approved what an authorized-looking request told it to approve. StepSecurity notes that Binance has not yet disclosed its token permissions, its signing-policy configuration or a full set of host indicators.
The Federal Bureau of Investigation (FBI) attributes the theft to TraderTraitor. CoinDesk describes the North Korean unit as the group behind several of the industry's recent high-profile thefts. The FBI also linked it to the roughly $1.5 billion Bybit theft in February 2025. TRM Labs counted about $6.36 billion leaving Binance wallets on ten blockchains and calls the theft the largest hack in history. North Korea rejects the attribution, according to SecurityWeek. Binance says it set aside about $6.34 billion of company funds to cover customers, and about $2.85 billion had been frozen or intercepted as of November 3, per BleepingComputer.
A smaller breach at Mercado Bitcoin, a Brazilian exchange, shows a similar failure in key management. Mercado Bitcoin announced on November 2 that it had contained an attack. On-chain data from Bitquery shows that 36,042 customer deposit addresses on Ethereum were emptied over the following four hours, as Goku Crypto News reported and CoinDesk confirmed. Bitquery puts total losses at about $48.5 million across ten chains. The exchange has estimated about $36.3 million. The deposit addresses signed the withdrawals themselves, so the attacker held the private keys or a system able to sign for them. No one has publicly attributed the Mercado Bitcoin attack. The exchange plans to restore balance viewing on November 9 and has given no date for withdrawals.
Part of a tracked trend
Losses Move to Components That Worked as Designed
A growing share of DeFi losses will come not from buggy contract code but from components behaving exactly as specified — oracle forwarders, validator signature sets, governance votes and other trusted off-contract inputs — so audits and bug bounties scoped to on-chain code keep missing the failure surface, and protocols will be repeatedly forced to extend review, scope and monitoring to their privileged operational infrastructure.
Start a discussion in Townsquare.
More from this edition
If the attribution holds, Pyongyang gains several billion dollars in hard currency that sanctions otherwise block, and Binance gains a narrative that a state attacker beat it rather than its own controls failing, while stablecoin issuers such as Tether and Circle gain proof that their freeze powers matter (reports put about $2.8 billion frozen).
The Federal Bureau of Investigation (FBI) and the blockchain firms TRM Labs and Chainalysis attribute the theft to TraderTraitor from on-chain and malware evidence they have not fully published, North Korea's official news agency (KCNA) carried Kim Yo Jong's statement calling the claim "absurd rhetoric", President Trump told reporters "We don't know if it's North Korea", and the fake-interview and internal-AI-tool account of how the attackers got in comes from Binance alone, which has not released its signing-policy configuration.
An open-source-intelligence read of how likely this story is true with its real nuance, not a judgment of any outlet. It assesses the claim, weighing independent and adversarial reporting. How we label confidence.
What this means
Both thefts went through the people and machines that hold signing authority, which code audits do not cover. The losses fall on exchange balance sheets, on customers of venues that lack Binance's capital, and on stablecoin issuers and lenders now asked to freeze stolen funds. The Bybit theft is the closest precedent. Bybit covered customers, kept operating, and most of the stolen funds were laundered before anyone could freeze them. Binance's $2.85 billion in early freezes is a different outcome, and the main reason is how much of the stolen value sat in tokens whose issuers can freeze them. The consensus treats this as an exchange-specific failure. The evidence points instead to a repeatable playbook: fake hiring processes, compromised developer machines and signing services that trust deployed code. The likelier outcome is that within months the large exchanges move signing behind hardware-isolated policy engines, restrict EIP-7702 delegations from hot wallets, and give insurers and auditors scope over developer laptops. That depends on Binance publishing enough detail for peers to copy its fixes. The read is wrong if another exchange loses a nine-figure sum through the same developer-machine route before year end.
What to watch
Observations to monitor, not financial advice.
Synthesized from: CoinDesk · Polylog editors
Comments
1Nov 6, 9:52 AM · edited
A stolen container deployment token was enough to run code that reached the wallet signing service, which places the deploy pipeline inside the signing trust boundary at Binance.