The largest theft in the history of cryptocurrencies now has an official author. The FBI attributed the attack on Binance, valued at around 6.3 billion dollars, to TraderTraitor, the state-sponsored North Korean cyberwarfare unit that has spent years pursuing exchanges and institutional wallets. The news came on Sunday, November 1, two days after the company acknowledged that a compromised service container had issued unauthorized withdrawals across ten different networks. The case has been told in three pieces: the timeline of the night of the 29th, the first damage estimate and the reading on what the sector loses.
The figure is not an accounting detail. Binance has internally set aside around 6.34 billion to cover the affected balances and says it has replaced 90% of the total, charged to the Secure Asset Fund for Users, the futures insurance fund and corporate treasury. A remaining 10% is in less liquid tokens, the part of the haul that cannot be rebuilt by buying on the market without moving the price of those assets.
For the Spanish user who trades on centralized exchanges, the episode has an immediate reading: custody stopped being a password problem and became an internal architecture problem. A DevOps engineer with access to a poorly segmented container was enough to drain wallets on XRP Ledger, Ethereum, Bitcoin, Tron, Solana and six other networks. The chain of failures was short and boring, which is how expensive incidents usually are. Concentration also carries a price that no one bills until it has to be paid: custody in a single place simplifies daily operations, multiplies the damage of an internal failure and leaves thousands of users without access at the same time.
The attribution that was missing
Until Friday, October 30, the only public clue was a TRM Labs report pointing to Lazarus based on similarities with previous thefts. The FBI's confirmation changes the status of the case, because TraderTraitor has its own name on US sanctions lists and that opens the door to legal measures that do not depend on the private investigation. Formal authorship also brings the machinery that was already activated in previous cases: seizures, sanctions on mixer addresses and pressure on the exchange services that receive those funds.
The speed of the announcement matters. In the 2025 Bybit hack, attribution took days and the market priced in the worst-case scenario for a full week. Here the North Korea label arrived in less than 72 hours and the price of bitcoin rose 0.7% to 78,120 dollars, with ether around 2,268 dollars. The market decided the problem belonged to Binance and not to the sector.
That reading makes sense in the short term and is probably premature. When the party responsible is a state actor, recovering funds is almost impossible and the portion that is frozen never comes back in full. What the market is rewarding is not the resolution of the case but certainty about who pays the bill. And that certainty was provided by the company itself on Saturday, when it announced that users would not bear the financial impact.
Users' memory shortens as soon as the money is back in the account, and the platform recovers volume before reputation. That order suits the business and says nothing about security. The certainty that arrived on Saturday separates two things that are often confused: covering the accounting hole and guaranteeing that the user's money remains available when they want to move it.
How do you replace a 6.3 billion hole?
Replacing 90% of a haul this size in less than 48 hours requires three sources of liquidity. The first is SAFU, the emergency fund Binance holds with 1 billion in stable assets and which has served as a declared buffer since 2018. The second is the derivatives insurance funds, reserves the company accumulates from part of its futures fees.
The third is corporate treasury, the opaque part of the exercise. A firm that trades on private markets does not have to detail how much of its own balance sheet it devotes to plugging a hole, and that leaves an open question about the health of its operating reserves. The figure of 6.3 billion that the company acknowledged on October 30 serves as the basis for all the calculations that follow. The move closed with a decision that also carries a cost: withdrawals were suspended from the night of the 29th and only reopened on Sunday, with more than 48 hours of blockage for customers.
That blockage is the part of the episode that most affects the ordinary user. An exchange can have funds to spare and still prevent you from taking out yours for two days, because the priority is the accounting, not your liquidity. For anyone who uses the platform as a crypto checking account, the real scare was not the hack but discovering that access to their own money depends on the company closing an internal reconciliation.
The distinction between solvency and availability is learned the hard way, and almost always at the worst moment. A balanced balance sheet and a closed door can coexist without technical contradiction, even if for the customer the difference is hard to distinguish in the heat of the moment.
What does proof of reserves cover and what does it leave out?
Binance took a new snapshot of assets at midnight GMT on Saturday to update its proof of reserves. The list of included tokens is broad and covers the ten affected networks, with a minimum one-to-one backing committed once the full proof is available.
- Bitcoin (BTC) and ether (ETH)
- USDT, USDC, USD1 and RLUSD
- BNB, solana (SOL), XRP and zcash (ZEC)
The technical detail worth reading closely is scope. A proof of reserves demonstrates that the declared liabilities are covered by assets at a specific moment. It does not demonstrate that those assets are free of liens, nor that the keys are genuinely segregated, nor that cold wallets do not share custody with hot wallets. Nor does it cover the illiquid 10% or say anything about off-balance-sheet liabilities.
There is an asymmetry that exchange users tend to ignore: the proof is published after the incident, with the perimeter already rearranged. Whoever looks at the report sees what the company wants to show and at the moment it wants to show it. It is better than nothing and still insufficient as a legal guarantee, because the holder of the assets remains the platform and not the customer.
For readers who have spent years calling for a proof of reserves with verifiable cryptographic commitments, the episode leaves an uncomfortable lesson. Ten affected networks, one container and a compromised automation. None of those pieces is detected by looking at a merkle hash.
The trail of the 3 billion frozen
Alongside the replacement, Binance coordinated with industry partners the freezing of around 3 billion dollars, almost half of what was taken. The figure sounds like a victory and is worth putting in context: frozen funds are not recovered funds. The money exists, is identified and in theory still belongs to customers, but its return depends on legal proceedings that in previous cases have taken years and returned a fraction.
The other half is probably no longer in a recognizable format. Lazarus's pattern in previous operations combines rapid mixing, conversion to stable assets on chains with little oversight and transfers to exchange infrastructure without strict controls. With 6.3 billion at stake, the trail becomes months of work for forensic analysis firms that charge by the hour and compete to claim credit for the finding.
European exchanges operating under MiCA have an additional obligation that almost no one has mentioned. They must apply enhanced due diligence measures to addresses operating from high-risk jurisdictions and report suspicious transactions within short deadlines. If those 3 billion try to pass through a platform regulated in the European Union, the trail should be recorded.
That trail is today the only realistic route to recovery. There is no bailout, no public insurance and no fast court for a haul that travels in seconds from one chain to another without asking anyone's permission.
The custody standard must evolve
Binance will survive the episode and will probably regain its customers' trust within weeks, as has happened in every previous crisis. What does not go back is the accumulated evidence on how these platforms break. They are not brought down by theoretical attacks or cryptographic vulnerabilities, but by poorly segmented internal access and processes that rely on a single piece.
The contrast with the 2025 Bybit theft is useful because then the vector was an external provider with access to signatures. Here it was the company's own infrastructure. Two years, two lessons and the same underlying pattern: concentrated liquidity tempts, operations are optimized for speed and security is added afterwards.
Anyone holding significant amounts on an exchange should take away more than an anecdote. The right question is not whether the platform has an emergency fund, but how long it takes to give you back access when something fails and who signs off on the operation when 6 billion has to be moved in one night. If the answer to either is blurry, the hack figure is not the important data point of the weekend.