Urgent alert — confirmed

Binance Hit by the Biggest Crypto Hack in History: $6.3 Billion Stolen

A compromised DevOps engineer's laptop. Access to an internal service. Unauthorized withdrawals across ten blockchains in about 20 minutes. Binance confirmed the incident itself — and two independent blockchain analytics firms point to North Korea.

October 30, 2026 · SunuCyberSecurity Team · Updated November 1, 2026

Partager :WhatsAppFacebookLinkedInX
$6.3B

total impact estimated by Binance itself, including funds already frozen

~$3B

already frozen on-chain, including $2.3B in USDT/USDC stablecoins

~20 min

time TRM Labs estimates for most of the theft, spread across 10 blockchains

4%

share of the ~$144B in assets Binance held before the incident (DefiLlama)

Sources: CoinDesk, CNBC, Cybernews, Forbes, Yahoo Finance — full list at the end of this article. The situation is evolving quickly.

On October 29, 2026, Binance, the world's largest crypto exchange by volume, was exploited for more than $6 billion — making it, according to several experts cited by CoinDesk, the largest crypto theft on record. The exchange itself estimated the total impact of the incident at roughly $6.3 billion and suspended withdrawals shortly after, pending resolution of the issue.

How the hack happened

Per Binance's own preliminary investigation, the incident appears to trace back to a compromised laptop belonging to a DevOps engineer. That compromise reportedly let the attacker reach an internal "service container" and submit unauthorized withdrawal transactions. Binance stressed one important point: no evidence of a wallet private-key leak was found — meaning the attack appears to have gone through a system-level access path rather than a stolen cryptographic key.

It's an attack pattern worth taking seriously well beyond the crypto world: a single compromised individual workstation that, by extension, opened access to critical infrastructure capable of executing irreversible financial actions. The failure point wasn't the blockchain itself, but the boundary between a user endpoint and the internal systems it could reach.

The scale of the theft — figures vary, the order of magnitude doesn't

As with many incidents of this scale analyzed in real time, the numbers differ slightly depending on the method and source — without changing the order of magnitude. Binance cites $6.3 billion in total impact. Blockchain analytics firm Chainalysis put the theft at roughly $5.9 billion at the time it happened. TRM Labs, for its part, tracked roughly $6.36 billion in outflows across ten different blockchains, with most of the theft occurring in just about 20 minutes. Per Arkham Intelligence, the hacker's wallets at one point held more than $5.7 billion across various crypto assets: close to $1.5 billion in bitcoin, $900 million in ether, roughly $1.5 billion in USDT, and over $800 million in USDC.

Measured against the roughly $144 billion in assets Binance held before the incident (per DefiLlama), the theft would represent about 4% of the platform's holdings.

The race against time to freeze the funds

Within the first hours, Binance announced it had already frozen roughly $3 billion in assets, including $2.3 billion combined in USDT and USDC stablecoins — possible because those tokens have a centralized issuer able to block transfers. Tether (Paolo Ardoino) confirmed freezing over $1.57 billion in USDT linked to the incident, and Circle (Jeremy Allaire) over $800 million in USDC.

The attacker, meanwhile, has clearly been trying to escape those freezes by moving funds into decentralized assets with no central issuer able to block them: movements through the decentralized exchange Uniswap were spotted, along with a roughly $44 million loan in wrapped ether (WETH) through the lending protocol Aave, using stolen USDT as collateral. Part of the stolen bitcoin — roughly $1.4 billion per later tracking — was reportedly also split across 19 separate wallets to complicate any freeze or trace attempt.

Who's behind the attack

Several independent investigators converge on the same origin, without using exactly the same group name — a nuance worth keeping rather than flattening into one single label. Security firm Blockaid (its CEO Ido Ben-Natan, quoted by CoinDesk) said the sophistication observed so far "is consistent with the kinds of operations we've seen from DPRK." TRM Labs said it traced the attack to TraderTraitor, an elite North Korean hacking group, with what it describes as high confidence. Prominent blockchain investigator ZachXBT instead points more specifically to the Lazarus Group — the North Korean state-sponsored hacking squad already tied to numerous crypto thefts — as the likely attacker.

This isn't an isolated event for the ecosystem: in September 2026, the same month, exchange Bitget had already suffered a theft of over $350 million, and Chainalysis says it spotted funds from that incident commingling with the Binance loot — a sign that the same, or linked, actors have been operating continuously against several targets in the sector.

Update — November 1, 2026

The FBI officially confirms the TraderTraitor attribution

On November 1, 2026, the FBI, together with the U.S. Secret Service (USSS) and the IRS Criminal Investigation unit (IRS-CI), officially attributed the theft to TraderTraitor — a North Korea-aligned elite hacking group also tracked as Jade Sleet, Pressure Chollima, PUKCHONG, Slow Pisces, and UNC4899, active since at least 2020. This is a change in kind, not just degree: the section above described estimates from private analytics firms (TRM Labs, ZachXBT); this is now an official attribution from three U.S. federal agencies.

The agencies said they observed the threat actor converting most of the stolen assets into Ethereum (ETH), ahead of further laundering through DeFi and instant-swap services. The FBI published a list of wallet addresses used in this laundering phase, intended to help platforms and exchanges block the funds involved. A new frozen-funds total was reported: $2.85 billion, across Tether, Circle, Ripple, Arbitrum, and Optimism — close in order of magnitude to Binance's own initial ~$3B estimate, but a separate measurement from different issuers.

On the operational side, Binance announced it has resumed phase one of withdrawals, starting November 1 between 6 and 9 a.m. UTC, after completing its security checks. Deposits were never affected by the incident.

For context on the threat: reporting from Microsoft, SentinelOne, and Zscaler ThreatLabz shows TraderTraitor continuing to refine its tradecraft beyond crypto theft — including trojanized Terraform providers as a cross-platform malware distribution vector, and AI-assisted fake-recruiter campaigns (fake personas, fake front companies) targeting cybersecurity, AI, and blockchain professionals. The same actor behind the Binance theft is documented running these targeted social-engineering campaigns in parallel — further confirmation this is a structured state actor, not an isolated opportunistic one.

Are user funds safe?

Binance co-CEO Yi He posted on X that the platform would cover all losses from the hack, drawing on the SAFU (Secure Asset Fund for Users), a reserve fund created in 2018 specifically for this kind of scenario and holding roughly $1 billion in bitcoin, backed up by the company's own funds. Binance founder Changpeng Zhao (CZ) — who no longer runs the exchange day to day — also publicly said user funds were safe, adding that as a shareholder he expected them to be fully covered.

The news still rattled markets: bitcoin fell nearly 5% below $77,000, ether dropped about 5.7%, and the BNB token fell 8% on the day of the announcement.

Why this matters for francophone Africa

Binance is one of the most widely used crypto exchanges in francophone Africa, particularly for trading and cross-border transfers in contexts where access to foreign currency can be constrained. The global withdrawal suspension therefore concretely affects users in the region too — not just the Western markets making the headlines.

But the underlying lesson reaches well beyond the crypto world: a single compromised workstation — an engineer's, not an executive's — was enough to expose several billion dollars in assets. That's exactly the kind of risk any organization faces when a critical internal access point is reachable from an insufficiently segmented user endpoint, whether or not it handles crypto assets.

Security lessons to take away

Isolate high-privilege workstations

A DevOps engineer's workstation should never, on its own, be able to reach an internal service capable of triggering withdrawals or other irreversible actions — a local compromise shouldn't be enough to gain production access.

Apply least privilege to internal services

A "service container" that executes sensitive transactions should require more than a compromised user session: just-in-time access, multi-party approval, network segmentation, and strong MFA for any high-impact financial action.

Prepare a coordinated freeze response

Tether and Circle freezing over $2.3 billion within hours shows the value of fast coordination with stablecoin issuers and blockchain analytics firms at the first signs of a fund leak.

Track the North Korean state-actor threat

TraderTraitor/Lazarus Group have repeatedly targeted the crypto ecosystem (Bitget in September, Bybit in 2025, now Binance) — a specific risk any organization holding or handling digital assets should factor in.

Sources and methodology

CoinDesk (Binance's official statement, Arkham/Chainalysis figures, Blockaid/TRM Labs/ZachXBT attribution quotes, Uniswap/Aave fund movements) · CNBC · Cybernews (North Korea attribution) · Forbes (technical mechanism) · Yahoo Finance · The Hacker News (official FBI/USSS/IRS-CI attribution, November 1, 2026, plus Microsoft/SentinelOne/Zscaler ThreatLabz reporting). Incident publicly confirmed by Binance on October 29, 2026. Initial data as of October 30, 2026, updated November 1, 2026 with the FBI's official attribution — the situation is still evolving; we will update this article if significant facts change.

Related reading

Claimed Orange Data Leak: What We Know (and What's Still Unconfirmed) PHP2Shell: Two Critical RCE Flaws Force an Emergency PHP Patch

Check your own exposure

A free scan, in minutes, no credit card required.

Free scan

Newsletter

Get our next analyses

One email whenever we publish a new article. No spam, one-click unsubscribe.