$6.3 billion left Binance in 20 minutes — most of it is frozen, none of it broke the market

Asked:
“do a good research on the binance hack and who sid it the market loss the crises”
Asked (follow-up):
“do better and you have not given any graph use graphs to represent”

Twelve graphs built from 182 dated, sourced observations — 12 running estimate snapshots, 145 market observations from Oct 29–31 2026, 7 token-level rows and 13 cleaned historical hack incidents — drawn from 108+ independent news and research hosts. Research current through October 31, 2026. All dollar figures are USD; hack sums in billions.

Who likely did it?

TRM Labs and Chainalysis attributed the operation with high or likely confidence to the North Korea–linked TraderTraitor cluster, associated in reporting with the Lazarus ecosystem (securityweek.com). This remains analytical attribution, not a public final criminal judgment: Binance has not conclusively named the attackers, and North Korea denies such cyber-theft allegations.

How the attack worked

Reporting points to compromised transaction-signing infrastructure. The initially suspected DevOps laptop was only part of a more complex intrusion with additional breach points, and malware reportedly deleted evidence of its own activity (thenextweb.com, jpost.com). Binance said it found no evidence that wallet private keys leaked. Attack-chain illustration (not a graph):

Initial intrusion incl. DevOps laptop
→
Signing infrastructure compromised
→
~$6.3–6.4B drained across ~10 chains in ~20 min
→
Evidence-deleting malware
→
Laundering; issuers and chains freeze funds

Why the crisis did not become a solvency collapse

This was a severe crypto-market shock, not a global financial crisis. Freezes by Tether, Circle, Ripple and others locked billions within hours; later reporting put frozen or recovered assets as high as $5.67B. Binance committed SAFU and company resources, set aside about $6.34B and said users would be made whole (shattered.io). Prices fell 3–8% and partially rebounded; not every move in those days was caused solely by the hack.

What remains uncertain

Sources disagree on totals: stolen estimates span $5.5–6.4B, frozen/recovered $2.4–5.67B and still-exposed $1.85–3.3B at different times — these are dated snapshots and are never added together here. Attribution confidence varies by firm; the single-source $5.67B recovery figure and some token-level amounts (e.g. the XRP and ARB rows) rest on one outlet each and should be read cautiously. Reuters-syndicated, major-news, Binance, Arkham, TRM and Chainalysis reporting was preferred over aggregators.

Market observations, Oct 29–31

Observed (UTC)BTC $ETH $BNB $Liq. $B/24hSource

Method: 182 deduplicated web observations gathered Oct 29–31 2026 across 108+ hosts: 12 running-total snapshots (stolen / frozen / exposed / coverage, USD billions), 145 market observations (spot prices in USD, reported %-change windows of varying length, 24h liquidation totals in USD billions — overlapping windows, never summed), 7 token-level rows (null = not established) and 18 historical incidents cleaned to 13 (duplicate Coincheck/Mt. Gox/Binance rows and one null row removed). Charts omit nulls and one implausible sub-$100 ETH price; percentage plots keep values between 0 and −12%. Detail text trimmed for space.

This report was generated automatically by Keenable SELECT at a user's request, from publicly available web sources linked herein. Keenable does not review, verify, or endorse its contents and makes no representation as to accuracy, completeness, or timeliness; AI-based extraction may contain errors. Nothing in this report is investment, legal, financial, or other professional advice. All trademarks and referenced content remain the property of their respective owners; no affiliation or endorsement is implied. To report an error, rights concern, or request removal: legal@keenable.ai.

Keenable SELECTAsk your own question
Made with Keenable SELECT