Finance

Binance’s $6.3B Hack: What Bybit and Ronin Reveal

Binance’s $6.3 billion hack dwarfs Bybit and Ronin. Its 90% replenishment is not recovery of stolen funds. The cases show how custody controls can fail.

2026.11.01 · By dvdmaru · ~11 min read · 2,464 words
閱讀中文版

At about 4:05 a.m. on October 30, 2026, Taipei time (October 29 at 20:05 UTC), unauthorized transfers began draining Binance’s hot wallets. The exchange estimates that roughly $6.3 billion in token assets was stolen. Blockchain intelligence firm TRM Labs says most of the funds moved in about 20 minutes and calls this the largest known single cryptoasset theft by dollar value. Binance’s second update (in Chinese), TRM Labs

On October 31, Binance announced that it had replenished approximately 90% of the affected assets. That is meaningful progress toward filling the platform’s shortfall. It says much less about how much money has been recovered from the thieves.

Comparing this breach with Bybit in 2025 and Ronin in 2022 reveals a problem that a league table of losses would miss. A wallet is only one part of custody. The authority to move assets also passes through people, software interfaces and organizational procedures. A failure along that path can undermine protections that remain valuable in their own right.

Binance halted withdrawals as investigators found more entry points

Hot wallets connect to online systems to support routine transfers. Cold wallets keep private keys isolated from that environment. A private key is the credential used to authorize a transfer; access to signing capability can therefore be as consequential as access to the assets themselves.

Binance initially said a compromised DevOps engineer’s laptop might have allowed an attacker to access a backend service environment and submit unauthorized withdrawals. Its second update added that investigators had found other points of breach. At that stage, the company said it had found no evidence that wallet private keys had leaked. Initial announcement, second update (in Chinese)

That leaves “one hacked laptop lost $6.3 billion” as an incomplete explanation. A laptop may be an entry point. Investigators still need to establish how the attacker acquired further privileges, which controls failed to stop the transfers and why so much could move so quickly.

TRM observed an EIP-7702 delegation on Ethereum: an authorization allowing a wallet to execute specified code. In this case, the code was controlled by the attacker and drained the wallet’s assets. On other chains, TRM observed ordinary signed transfers. It assessed this as evidence that the internal systems signing Binance’s hot-wallet transactions had been compromised. This need not contradict the statement about private keys. TRM and Elliptic assess that the attacker may have made Binance’s own systems sign transactions, without necessarily taking the keys away. These remain researchers’ assessments, not Binance’s completed root-cause report. The Ethereum mechanism does not, by itself, explain the breaches on other networks. TRM’s technical analysis, Elliptic

Binance revoked affected authorizations, suspended withdrawals and worked with law enforcement and token issuers to freeze assets. Its third update still targeted November 1 for reopening withdrawals. Replacing missing assets, completing security checks and making withdrawals available are separate tasks. Progress on one does not establish completion of the others. The replenishment announcement needs to be read with those distinctions in mind.

Freezing $3 billion and replenishing 90% address different shortfalls

Binance has promised to absorb the financial loss. Understanding its progress requires separating where the stolen assets are from who is paying to replace them.

Announced measureWhat it describesWhat it does not establish
Roughly $6.3 billion stolenBinance’s estimate of assets transferred without authorizationThe final, unrecoverable net loss
Roughly $3 billion frozenBinance says it worked with law enforcement, issuers and other partners to freeze the assets on-chainReturn to Binance or availability for customer withdrawals
Approximately 90% replenishedBinance says replacement coverage has reached approximately 90%Recovery of 90% of the assets from the attacker

Sources: Second update (in Chinese), third update.

A freeze and a replacement purchase can cover the same missing assets. The stolen tokens may remain blocked in an address while the exchange uses its resources to fill the shortfall. Adding the two measures would double-count progress; subtracting them does not calculate the exchange’s final loss either. That depends on what is ultimately returned and how the recovery is resolved.

The second update said Binance had set aside more than $6.34 billion in company funds, with over $5 billion in corresponding tokens already in place. The third raised coverage to approximately 90%, without breaking down existing holdings and subsequent purchases. That percentage cannot be read as an amount entirely bought after the incident.

The third update lists resources including the Secure Asset Fund for Users, or SAFU, part of the futures insurance fund and Binance’s corporate treasury. It says part of the SAFU deployment is expected over the following 24 hours to help acquire the remaining tokens. Binance says ten assets, including BTC, ETH and USDT, are fully backed, while the remaining approximately 10% consists of less liquid tokens still being purchased through markets and over-the-counter channels. Setting aside dollars and obtaining all the required tokens are different stages of replenishment.

To let customers check asset backing, Binance published a Proof of Reserves, or PoR, snapshot taken at 8 a.m. on October 31, Taipei time, with a full zero-knowledge proof to follow, allowing users to further verify asset backing through cryptographic methods. A snapshot can help test asset backing at a particular moment. It does not replace a financial-statement audit or a security investigation. In a 2023 advisory, the Public Company Accounting Oversight Board’s (PCAOB) Office of the Investor Advocate explained that third-party PoR engagements are not audits and do not provide assurance over the effectiveness of internal controls or governance. That is a general limitation, not an assessment of Binance’s new snapshot. PCAOB investor advisory

Even if the assets are replaced, the custody failure still needs an explanation. Two earlier incidents with fuller investigations show how approval can go wrong outside the wallet itself.

Bybit and Ronin failed at different approval points

The figures below use the cited sources’ estimates for each incident, rather than repricing the stolen tokens today. Ronin’s attack occurred on March 23; it was discovered and reported on March 29.

Incident and attack datePublic dollar estimateCustody or approval system affected
Binance, October 30, 2026, Taipei timeAbout $6.3 billion, according to BinanceHot wallets and related infrastructure; the full intrusion sequence remains under investigation
Bybit, February 21, 2025About $1.5 billion, according to the FBIA cold-wallet transfer’s signing interface and Safe’s development environment
Ronin, March 23, 2022About $620 million, according to the FBIThe five-of-nine validator threshold required by the bridge at the time

Amount sources: Binance (in Chinese), FBI on Bybit, FBI on Ronin. Technical accounts follow below.

Amount note: TRM estimates $6.36 billion across ten chains; Elliptic estimates $6.43 billion across eleven. Their coverage and observation times differ, so the discrepancy cannot be reduced to rounding. The table uses Binance’s approximate $6.3 billion estimate. TRM, Elliptic

Bybit: offline keys still depend on a trustworthy signing process

The Bybit theft occurred during a routine transfer out of cold storage to an operational wallet, described by Sygnia as a warm wallet. Sygnia, which investigated the incident, describes a sequence beginning with the compromise of a Safe developer’s workstation. The attackers obtained cloud access credentials and altered the frontend code behind the signers’ interface. Authorized signers believed they were approving a normal transfer; the transaction they actually approved gave the attacker control of the wallet. Sygnia’s forensic case study

Bybit’s preliminary forensic update likewise identified compromised Safe developer credentials and deceived signers. Bybit’s update

Sygnia explicitly describes an attack on trust in the interface, rather than on cryptography. Sygnia’s case study

Cold storage still serves a purpose: it reduces the keys’ direct exposure to online threats. But moving assets requires someone to decide what to sign. If several approvers rely on the same compromised display, several people may approve the same harmful action. Requiring more signers and giving those signers reliable, independent ways to check a transaction solve different problems.

Ronin: nine validators did not mean nine independent risks

Ronin’s bridge connects Ronin and Ethereum, allowing assets to move between the networks. The stolen holdings were 173,600 ETH and 25.5 million USDC. According to an archived copy of Ronin’s official community alert, validators were the nodes responsible for checking and signing transactions; withdrawals required five signatures from nine validators at the time. Archived official alert

The attacker gained control of four validators operated by Sky Mavis. The fifth signature came from Axie DAO. In November 2021, amid heavy user demand, Axie DAO had allowlisted Sky Mavis to sign transactions on its behalf to help distribute free transactions. The service ended that December, but the permission remained. After entering Sky Mavis’s systems, the attacker used the still-open path to obtain Axie DAO’s signature and meet the four-plus-one threshold.

The attack happened on March 23. The team discovered it on March 29 after a user reported being unable to withdraw 5,000 ETH. The episode exposed both the concentration of effective approval authority and the delay in detecting an outflow.

Ronin was not an exchange, so it should not be treated as another exchange hot-wallet breach. Its relevance is more specific: a formal threshold involving several validators is only as independent as the underlying control relationships. Temporary permissions also need to expire in practice.

The FBI attributes the theft to North Korea; recovery remains a race

In a statement dated October 31, 2026, the FBI attributed the Binance theft to North Korea’s TraderTraitor actors. Its 2025 Bybit announcement used the same designation. For Ronin, the bureau’s 2022 statement named Lazarus Group and APT38. These are law-enforcement attributions. Related or overlapping group names do not establish that the same individuals carried out every attack. Binance attribution, Bybit attribution, Ronin attribution

The FBI says it has observed the stolen assets being converted primarily into ETH and expects further laundering through decentralized finance and instant-swap services. There is a direct incentive for that conversion. Some stablecoin issuers can freeze their tokens; Ether and Bitcoin have no equivalent single issuer with a freeze switch. FBI statement, Elliptic’s tracing analysis

Conversion does not make the funds untraceable or show that the thieves have cashed out. Assets can still encounter cooperating intermediaries or become subject to seizure. But the window in which an issuer can directly block movement may close when its token is exchanged. The attacker’s conversion speed competes with defenders’ ability to identify the flows and coordinate a response.

North Korean involvement deserves investigation, but the attribution alone cannot explain repeated success. The published material identifies Bybit’s compromised development environment and signing process, and Ronin’s validator permissions. Binance still needs to explain the entry points beyond the laptop and how the attacker acquired all the necessary internal privileges.

Analysis: loss coverage is a backstop, not proof of secure authorization

The following is an interpretation of the three cases.

A platform’s promise to absorb losses matters. Centralized management offers everyday convenience and may allow a company to mobilize funds and coordinate with issuers and law enforcement. If those arrangements deliver, customers may regain access to assets without waiting for every stolen token to be recovered.

The trade-off is exposure to the operator’s financial and operational resilience. A compromised signing system can put a large pool of assets at risk, while filling the gap depends on resources the company can actually deploy. A credible reimbursement commitment is worth verifying. It does not retrospectively establish that the custody process was secure.

Nor do these cases make individual safeguards worthless. Cold storage reduces key exposure; multiple signatures distribute approval authority; validator thresholds restrict unilateral decisions. The question is whether the protections remain independent in practice. Are several people checking the same display? Can one organization or delegation path influence several validators? Does a temporary permission actually stop working when it is withdrawn?

The next useful disclosures should therefore extend beyond a replenishment percentage. They should explain how transaction details can be reliably verified, how abnormal outflows can be caught earlier and how the attack path has been repaired. Full asset backing and functioning withdrawals are outcomes customers need. Forensic findings and control changes provide a basis for examining future risk.

Moving assets to a personally controlled wallet does not eliminate every risk. Self-custody can reduce dependence on an exchange, but it transfers responsibility for keys, backups and signing decisions to the holder. It is not a universal shortcut to safety. The stronger lesson from these incidents is that custody promises need verifiable authority and accountability behind them. Being able to cover a loss is a valuable buffer. Explaining how the risk of a repeat will be reduced is a separate obligation.

Frequently asked questions

Is Binance’s $6.3 billion hack the largest crypto theft on record?

TRM and Elliptic both describe it as the largest known single cryptoasset theft by nominal dollar value. Binance estimates about $6.3 billion, exceeding Bybit’s approximately $1.5 billion theft in 2025.

Does 90% replenished mean 90% of the stolen money was recovered?

No. Binance’s third update describes using company resources to cover the affected tokens, without saying the entire 90% was newly purchased. Freezing stolen assets, recovering them and replenishing platform holdings are separate measures of progress.

How could Bybit lose assets from a cold wallet?

Investigators found that attackers compromised Safe’s development environment and altered its frontend, deceiving authorized signers into approving a malicious transaction. Keeping keys offline does not remove the need to verify what is being signed.

What is Ronin, and how was its breach different from an exchange hack?

The Ronin case involved a bridge connecting Ronin and Ethereum, not an exchange. The attacker obtained the five signatures required from its nine validators at the time and withdrew the bridge’s assets; its validator threshold was compromised.


Scope: Information checked on the morning of November 1, 2026, Taipei time. Binance’s replenishment and withdrawal status follow its October 31 third update; reopening is a stated target, not a completed action established here. The Ronin source is a 2023 archive of the official alert containing later updates, not an exact snapshot of its initial publication. These cases illustrate mechanisms, not an industry-wide attack rate. Losses have not been repriced at current token prices. This is incident analysis, not a trading recommendation.