- Binance is investigating a record-breaking $6.36 billion cryptocurrency theft after attackers compromised its hot-wallet signing infrastructure across multiple blockchains.
- TRM Labs and Chainalysis have linked the attack to North Korea’s TraderTraitor group.
- Binance says it will cover all confirmed losses.
Binance is investigating a cryptocurrency theft estimated at $6.36 billion after attackers drained funds from its hot wallets across multiple blockchains on October 29, 2026, in what blockchain intelligence firm TRM Labs describes as the largest crypto theft on record.
The attack affected Binance wallets across ten blockchain networks, with most of the stolen funds transferred within approximately 20 minutes. Binance initially suspended deposits and withdrawals while investigating the breach, later confirming that deposits remained operational but withdrawals were still paused during security remediation.
TRM Labs and Chainalysis have attributed the attack to TraderTraitor, a North Korean state-sponsored hacking group. Binance has not independently confirmed the identity of the attackers. The exchange has pledged to cover all confirmed losses using its SAFU fund and corporate resources, while industry partners have helped freeze billions of dollars in affected cryptocurrency.
How the Binance Hack Happened
Binance’s initial investigation suggests that the attackers may have gained access through a compromised laptop belonging to a DevOps engineer. According to the exchange’s October 30 security announcement, the intrusion potentially allowed the attacker to access an internal service container and submit unauthorised withdrawal transactions.
I want to speak to you directly about what happened.
Bottom line – your money is safe, and we’re covering every loss.
Our initial investigation suggests this security incident may have started with a compromised DevOps engineer’s laptop. That gave an attacker access to a service container, where they submitted unauthorized withdrawal transactions.
To be clear: the attacker did not simply use one engineer’s permissions, and this was not a single “one-click” action. It involved a more complex attack process. Our investigation has not attributed responsibility to any individual.
So far, we have found no evidence of any wallet private key leak.
We’ll share a detailed technical post-mortem once the investigation is complete and every fact is verified – and publish an updated Proof of Reserves once remediation is complete.
What you need to know:
• Your funds are safe
• Binance will cover all losses from the SAFU fund and company funds
• Estimated total impact: ~$6.3B, with ~$3B frozen on-chain so far, in coordination with our blockchain partners
• No evidence of any wallet private key leak
• Deposits are unaffected and operating as normalWhat we’ve done:
• Temporarily suspended withdrawals while we complete a security revamp of the withdrawal service and its related addresses
• Revoked the affected address authorizations
• Engaged law enforcement and blockchain intelligence partners to trace and recover fundsOur team hasn’t stopped. We’re working closely with law enforcement to ensure the matter is handled appropriately – and I’ll share what I can, as soon as I can.
— Richard Teng (@_RichardTeng) October 30, 2026
Binance said it had found no evidence that wallet private keys were leaked. However, the exchange has yet to publish its complete technical post-mortem, meaning the precise intrusion method and full sequence of events remain under investigation.
TRM Labs’ blockchain investigation provides further insight into how the funds were moved. On Ethereum, the attacker allegedly exploited EIP-7702, a mechanism that allows an externally owned wallet to delegate transaction execution to smart-contract code. TRM says the attacker used 50 pre-signed authorisations to turn a Binance hot wallet into a wallet-sweeping mechanism under its control.
On the other affected networks, the attacker used ordinary signed transfers. TRM’s analysis suggests that the attackers obtained access to Binance’s hot-wallet signing infrastructure, enabling them to generate valid transactions across multiple chains.
The theft involved Ethereum, Bitcoin, Tron, XRP Ledger, Solana, Arbitrum, Optimism, Base, Avalanche and Polygon. TRM estimates that approximately $6.36 billion was transferred to attacker-controlled addresses, valued at the time of the transactions.
Read also: How to Keep Your Crypto Safe: A Practical Guide to Protecting Your Assets
Binance’s Response
Binance has pledged to cover all confirmed losses using its Secure Asset Fund for Users (SAFU) and additional company resources. In its October 30 announcement, the exchange said approximately $3 billion in affected assets had been frozen through cooperation with blockchain partners.
In a subsequent financial update, Binance said it had reserved more than $6.34 billion in company funds to cover the incident.
Binance has begun recovering affected assets for users and continues to work with law enforcement, issuers, blockchain intelligence firms and industry partners to trace, freeze and recover additional funds.
The company has already publicly committed to cover losses through company funds in the prior announcement.
Binance has already reserved over $6.34B of company funds to cover this incident. $5B of these funds are already held in the exact token assets that were impacted. We are completing the purchase of the remaining amount by buying token assets through market channels and OTC channels. We are doing this to match the format of the remaining token assets and address any asset shortfalls. This step can take longer because some tokens may have low liquidity and OTC settlement also takes time. We will share more progress as soon as we can.
These figures do not include frozen or protected assets, which remain subject to ongoing recovery and verification. Currently, $3bn has been frozen, with thanks to our industry partners. We are working with partners and law enforcement to recover the frozen assets.We will continue to use company resources to cover confirmed shortfall and will provide further verified updates as recovery efforts progress. Ultimately, all user funds will be verified publicly through our Proof of Reserves.
We will weather this storm. Thank you for the support.
— Binance (@binance) October 30, 2026
Approximately $5 billion is already held in the exact token assets affected, while the company is purchasing the remaining amount through market and over-the-counter channels. Binance said acquiring some tokens could take longer because of limited liquidity and OTC settlement requirements.
The recovery effort involves several cryptocurrency companies. Tether reported freezing approximately $1.57 billion, while Circle froze more than $800 million. Ripple also froze approximately $200 million in assets associated with the incident. These figures represent different stages and scopes of the industry’s response; they should not be treated as interchangeable with Binance’s evolving overall frozen-asset estimate.
Binance says it has begun recovering affected assets for users and will continue working with law enforcement, token issuers and blockchain intelligence firms. The company also intends to publish an updated Proof of Reserves after remediation is complete.
However, customer reassurance deserves scrutiny alongside the compensation commitment. CoinDesk’s analysis of Binance’s October 1 reserve data found that some wallets affected by the incident were included in the assets backing customer balances. Its analysis estimated that the loss could temporarily reduce ETH backing from 100% to approximately 94%, before replacement of the missing assets. Binance maintains that user funds are safe and has committed to covering the shortfall.
Deposits have returned to normal, but withdrawals remain suspended while Binance completes its security review. The exchange has indicated that it expects to restore withdrawals within 48 hours, although that remains a target rather than a guarantee.
Who Is Behind the Binance Hack?
Although Binance has not officially identified those responsible, blockchain intelligence firms TRM Labs and Chainalysis have linked the attack to TraderTraitor, a North Korean state-sponsored hacking group associated with the wider Lazarus Group ecosystem.
TRM Labs said its attribution was based on on-chain and off-chain intelligence, expressing high confidence in its assessment. The firm also identified similarities between the Binance incident and previous attacks associated with North Korean hackers. Reuters independently reported the attribution by the blockchain intelligence firms on October 30.
The most significant historical comparison is the February 2025 Bybit hack, in which approximately $1.5 billion in cryptocurrency was stolen. The FBI officially attributed that attack to North Korea’s TraderTraitor group, making it an established example of the group’s involvement in a major cryptocurrency theft.
Another relevant incident is the April 2026 KelpDAO hack, which TRM Labs also associates with North Korean-linked attackers. Its investigation identified similarities in operational preparations and fund movements, although the laundering techniques used in the Binance incident differed from those observed after the Bybit attack.
The Binance theft is significantly larger than the previous Bybit record. At approximately $6.36 billion, TRM’s estimate is more than four times the amount stolen from Bybit.
Read also: Bitget Confirms $351.6 Million Hack from Crypto Wallets
For Binance, the immediate priorities are completing the security investigation, restoring withdrawals and replacing the affected assets. For the wider cryptocurrency industry, the incident raises serious questions about the security of exchange wallet-signing infrastructure, internal access controls and the ability of attackers to exploit trusted operational systems without directly stealing private keys.
Binance says it will publish a detailed technical post-mortem once its investigation is complete. Until then, the precise entry point, full attack sequence and final attribution remain subject to further verification.
