Nov 02, 2026 · 8 min read
Binance $6.3B Heist: FBI Blames North Korea's TraderTraitor
On October 29, 2026, about $6.36 billion left Binance wallets on ten blockchains, most of it in roughly 20 minutes. Binance first pointed to a DevOps engineer's compromised laptop, then said it had found more points of breach. On October 31 the FBI named North Korea.
The largest crypto theft on record did not need a stolen private key. Binance says it has found no evidence one leaked. The attacker apparently needed a system already allowed to sign withdrawals, and a way to make it sign theirs. That moves the story from cryptography to something every engineering team owns: the path from a developer's laptop to production.
Key Takeaways
- Binance lost about $6.36 billion on October 29, 2026, moved out of its wallets on ten blockchains starting at 20:05 UTC, according to TRM Labs, roughly four times the $1.5 billion Bybit theft of February 2025.
- Binance's first explanation was that a compromised DevOps engineer's laptop gave the attacker access to a service container that submitted unauthorized withdrawals, but about six hours later it said it had uncovered additional points of breach.
- The FBI said on October 31 that North Korea was responsible, named the activity TraderTraitor, and published 628 addresses (608 Ethereum, 19 Bitcoin, 1 Solana) for exchanges to block.
- TraderTraitor has a documented habit of reaching crypto firms through engineers with fake recruiter approaches, but Binance has not said how the laptop was compromised.
- The early "$5.8 billion" headline was Arkham's valuation of 55 tracked addresses, not a Binance figure.
What Happened at Binance on October 29?
An attacker drained Binance hot wallets across ten chains in about 20 minutes, starting at 20:05 UTC, per TRM Labs. Binance paused deposits and withdrawals and revoked the affected address authorization.
At 02:25 UTC on October 30, Binance posted that its initial investigation "suggests that the security incident may involve a compromised DevOps engineer's laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions." It put the impact at around $6.3 billion, with about $3 billion frozen onchain, and promised to cover all losses.
TRM counts roughly $2.7 billion frozen, most of it stablecoins locked by their issuers. The attacker still held more than 420,000 ETH and 18,270 BTC, about $2.4 billion "beyond any issuer's reach."
Why Did the Number Change From $5.8 Billion to $6.3 Billion?
The figures measure different things at different moments. The "up to $5.8 billion" headline appeared on October 29, before Binance confirmed anything. BleepingComputer's first report explained that Arkham Intelligence's $5.78 billion was "the value of assets held across all tracked wallets," meaning 55 addresses under the label binance-hacker-1029. It was a balance snapshot, not a confirmed loss. Later counts:
- Binance, October 30: estimated total impact "around $6.3B."
- TRM Labs: approximately $6.36 billion moved out across ten blockchains.
- Chainalysis: about $6.4 billion, per CoinDesk.
- FBI, October 31: "more than $6 billion USD."
Counting outflows across ten chains catches more than one labeled cluster does, and prices moved during the swaps. Treat $6.3 billion as Binance's estimate and $6.36 billion as the most precise public count.
Did a DevOps Laptop Really Start It?
Possibly, but Binance has stepped back from making it the whole story. Binance chief Richard Teng wrote at 07:37 UTC that "the attacker did not simply use one engineer's permissions, and this was not a single 'one-click' action." Seventy minutes later, a Binance investigation update said the investigation "has uncovered additional points of breach" and called it "a complex attack."
No public statement says how the laptop was compromised. No phishing email, recruiter message or malicious package has been confirmed in this case. Until Binance's promised post mortem lands, any claim about the initial lure is speculation.
TRM's onchain analysis fills in the second half of the chain. On Ethereum, one transaction carried 50 signed EIP-7702 authorizations that turned a Binance hot wallet "into a sweeper it controlled," drained three minutes and 24 seconds later. Early indicators suggested the attacker had "phished the authorizations," but that leaves the other chains unexplained: their wallets use different key types, yet all produced valid signatures within about half an hour. TRM's conclusion: the attacker likely "gained the ability to make Binance's hot wallet signing system sign transactions of its choosing across chains."
That fits Binance's "service container" wording. The attacker did not need the keys. It needed the service allowed to use them.
What Did the FBI Say?
The FBI said North Korea did it. In an FBI alert issued Saturday, October 31, the bureau said the Democratic People's Republic of Korea "was responsible for the theft of more than $6 billion USD" from Binance "on or about October 29, 2026," and called the activity TraderTraitor, as BleepingComputer reported. The group is also tracked as Lazarus Group, Jade Sleet and APT38.
The alert lists 628 addresses: 608 on Ethereum, 19 on Bitcoin and one on Solana. The FBI, the Secret Service and IRS Criminal Investigation asked node operators and exchanges to block transactions "with or derived from" them. Chainalysis told CoinDesk the attackers had already used "thousands of addresses," so the list is a starting point. A day earlier, the FBI had only said it was "aware of the incident," according to Nextgov.
How Does TraderTraitor Usually Get In?
Through people who build and run the systems, usually engineers. The FBI, CISA and the Treasury described the pattern in April 2022 in advisory AA22-108A: intrusions begin with spearphishing messages to employees "often working in system administration or software development/IT operations (DevOps)," and the messages "often mimic a recruitment effort and offer high-paying jobs."
Later cases follow the same shape:
- DMM Bitcoin, May 2024, $308 million: a fake LinkedIn recruiter sent an employee of wallet vendor Ginco a coding test on GitHub that compromised the employee's computer; stolen session cookies did the rest, per BleepingComputer's account of the FBI findings.
- Bybit, February 2025, $1.5 billion: the FBI attributed the theft to TraderTraitor. The entry point was a Safe{Wallet} developer's macOS machine, and the attackers used that developer's live AWS session tokens, according to Safe's post mortem as summarized by Cointelegraph.
- Other North Korean units: the Drift Protocol theft (attributed by Drift to UNC4736) began with months of in person approaches to contributors, and the axios npm backdoor reached developers through their dependencies.
In TraderTraitor's two best documented thefts, DMM Bitcoin and Bybit, the attacker went through one person's workstation and then reused that person's live sessions. If Binance's post mortem confirms the laptop, the same move will have worked at four times Bybit's scale.
What This Means for Your Inbox
For engineers, the first contact in these campaigns is usually a message, often from a recruiter who does not exist. CISA's advisory tells companies to "implement email and domain mitigations" and train staff on spearphishing. A flattering job pitch to a DevOps engineer at a crypto firm deserves the suspicion of an unexpected invoice.
For Binance customers, the next wave is predictable. Binance itself told users to "rely only on official Binance channels for updates." Expect fake refund notices and "withdrawals resumed" emails built to harvest logins. The unrelated Chainalysis breach that exposed customer emails the same week shows how fast crypto contact lists become phishing lists.
What Should Engineers and Crypto Users Do Now?
Teams at any company that moves money should assume a developer laptop will be compromised, and design so that it is not enough. TRM's guidance and the CISA advisory point to concrete steps:
- Run take home tests and unknown repos in disposable VMs, never on the laptop that holds production credentials.
- Shorten and bind sessions. Bybit's attackers rode live AWS tokens; require hardware keys and device bound credentials for anything near signing infrastructure.
- Put policy in front of the signer. A withdrawal service should enforce velocity limits and a second approval for large batches, whoever reaches its container.
- Alert on EIP-7702 delegations. TRM says a delegation on a treasury wallet "should trigger an immediate alert," and signing policies should reject unexpected EIP-7702 authorizations.
- Block the FBI's 628 addresses and screen deposits against vendor labels, since Chainalysis says the real set is in the thousands.
For Binance users, the exchange says it has covered about 95% of the impacted amount and planned a first phase of withdrawals for November 1, per BleepingComputer. Ignore any email or DM about refunds or account checks and open the app directly. Turn on a withdrawal address allowlist and hardware key sign in.
What to Watch Next
The key document is Binance's technical post mortem. It should answer two questions: how the laptop was compromised, and why one service container could make signers on ten chains sign. TRM notes that "Binance has yet to publish a root cause." Until it does, the lesson from Bybit and the Bitrefill breach still applies: the weak point is one person's computer, and the damage depends on what it is trusted to reach.
The same day, a hijacked vendor script drained Polymarket traders' wallets, a reminder that attackers go around keys, not through them.