Binance Hacker Bitcoin Holdings Top Coinbase Treasury
A Binance attacker’s wallets held more BTC than Coinbase’s reported corporate treasury. See what the figures mean for custody, tracing and stolen crypto.

The Binance Hackers' Crypto Stash Was Bigger Than Coinbase's Bitcoin Treasury
On paper, it's a simple comparison: a major exchange's reported Bitcoin treasury versus the wallets linked to a hacker. In practice, the numbers are eye-catching but not the kind of apples-to-apples match you might assume.
On a Friday snapshot, addresses attributed to the Binance attackers behind the reported $6.3 billion breach held 18,270 BTC. Coinbase, meanwhile, reported 18,071 BTC for investment and operations at the end of September.
So the attackers came out ahead by 199 BTC. Bitquery also traced 508,621 ETH to the same group of wallets - more than the 495,362 ETH attributed to corporate treasury holder The Ether Machine. Still, these comparisons are helpful for scale, not for judging corporate wealth or total market supply.
The details matter. Coinbase's disclosed balance excluded customer Bitcoin, while the attackers' wallets represented assets linked to a theft, not a legitimate treasury. And these were snapshots, not proof that the assets could be sold or moved without consequence. This article breaks down what the holdings show, how to read the comparison, and why tracing stolen crypto is different from actually recovering it.
How did the attackers' Bitcoin holdings compare with Coinbase's?
Bitquery said 19 addresses linked to the Binance attackers held 18,270 BTC on the Friday snapshot. It valued that at roughly $1.4 billion. Coinbase reported, for September 30, 17,954 BTC held for investment plus 117 BTC for operations - 18,071 BTC in total.
That leaves a 199 BTC gap. It's enough to say the attackers' attributed balance was higher than Coinbase's reported corporate holdings - but it doesn't tell you who had "more money" in any meaningful financial sense. This is a visible balance matched to another visible balance, while skipping the hard parts: who controls the assets, what they're for, and what access actually looks like in real life.
Coinbase's figure was its own corporate Bitcoin holdings. It did not include Bitcoin held for customers. That distinction is key: customer balances sitting on an exchange's platforms aren't the same thing as assets the exchange owns. So the comparison doesn't say anything about Coinbase's total customer assets or its overall balance sheet.
The attackers' figure has its own limitation. It's based on blockchain attribution, not an audited corporate balance. The assets were allegedly stolen, and the attribution depends on how convincingly analysts can connect the wallets to the breach. A wallet balance tells you what's on-chain at a point in time - it doesn't, by itself, prove legal ownership or that the holder can safely turn the assets into cash.
A headline comparison, not a treasury ranking
BitcoinTreasuries.net ranked Coinbase eighth among publicly traded companies based on its 17,954 BTC investment balance. That ranking is about corporate holdings, not every Bitcoin controlled by an exchange - and not funds tied to a reported theft.
It's still useful as a quick "how big is this?" framing. Just don't read it as evidence that the attackers had a legitimate treasury larger than Coinbase's. In finance, terms like held, owned, custodied, and attributed to aren't interchangeable.
What do the Bitcoin and Ether figures actually measure?
The numbers come from two different worlds: on-chain address data and company disclosures. That means they answer different questions. Bitquery traced crypto to addresses it associated with the attackers. Coinbase reported Bitcoin balances for specific corporate purposes as of a reporting date. One is an analytics estimate tied to suspected criminal activity; the other is a company-reported balance with defined categories.
That difference matters for both the Bitcoin and Ether comparisons. Bitquery traced 508,621 ETH to the attackers on the same Friday snapshot. BitcoinTreasuries.net attributed 495,362 ETH to The Ether Machine and ranked it third among corporate Ether holders. On those figures, the attacker-linked wallets were ahead by 13,259 ETH.
But the ETH comparison still isn't proof that the attackers had greater overall wealth than a company. It compares token quantities, not total assets, liabilities, market value at a single valuation moment, or practical ability to transact. The report did provide an approximate dollar value for the 18,270 BTC - but token counts alone shouldn't be treated like a complete financial valuation.
Why a wallet balance is not the same as usable money
A blockchain balance is visible, but visibility doesn't automatically mean liquidity. Moving a large position can attract scrutiny from exchanges, investigators, and other market participants. If a recipient address is flagged, a centralized platform may delay or block deposits while it checks the origin. Even for attackers, operational frictions - splitting funds, swapping assets, or attempting to cash out - can slow things down or complicate execution.
There's also the control issue. Analytics can sometimes map relationships between addresses and track flows, but they generally can't undo transactions or seize assets on their own. A wallet can be right there on-chain while the assets remain effectively unreachable to the victims - and out of an exchange's immediate control.
Key takeaways:
- The BTC comparison was 18,270 BTC attributed to attacker-linked addresses versus 18,071 BTC reported by Coinbase for investment and operations.
- Coinbase's figure excluded customer Bitcoin.
- The ETH comparison was 508,621 ETH attributed to the attackers versus 495,362 ETH attributed to The Ether Machine.
- These were reported snapshots, not proof of ownership, liquidity, or recoverability.
How did the attackers build and hold the crypto stash?
The reported attack affected nine blockchains in less than four hours, according to the source account. Bitquery said the attackers initially stole 200,630 ETH, then increased their Ether balance by swapping stolen stablecoins and other tokens. That helps explain why the final ETH figure could be larger than the amount of Ether described as taken at the start.
This matters operationally. A breach doesn't always boil down to one asset moving straight from a victim's wallet to an attacker's. Stolen tokens can get exchanged across assets or chains, which changes balances over time and makes incident response harder. Investigators then have to follow transaction flows across networks, figure out where funds are consolidated, where they're split, and how they're converted.
Bitquery's snapshot showed 17 attacker-linked Bitcoin addresses holding 1,000 BTC each, with the rest in two other wallets. Concentration can make the holdings easier to summarize - but it doesn't fully reveal strategy. Address structure is only part of the story; analysts still need to look at transaction history, timing, and connections to other wallets to judge whether funds are related.
Attribution remains a developing investigation
TRM Labs attributed the attack to North Korea's TraderTraitor hacking group. Binance said investigators found additional breach points after initially suspecting a DevOps engineer's compromised laptop. Those statements point to an investigation that keeps evolving, not a complete public account of every entry point and operational detail.
That uncertainty is normal. Early theories shift when investigators review logs, infrastructure, and on-chain movement. And attribution at the "group" level isn't the same as identifying the individuals who executed a specific transaction or proving responsibility in court. For now, the public should treat named attribution as an assessment that could change as more evidence comes in.
For exchanges, the incident highlights why response work spans more than one system. A wallet breach can touch key management, access controls, deployment processes, monitoring, and incident coordination. The question isn't just "how much crypto left a wallet?" It's also "how did the attacker gain the ability to move it - and could the same weakness affect other assets or services?"
Can blockchain tracing lead to frozen or recovered funds?
Binance said about $3 billion in stolen assets had been frozen and pledged to cover all losses. That's a major reported response - but "frozen" and "recovered" aren't the same thing.
Freezing depends on where and how the assets move. It may involve cooperation from a centralized service, a protocol, or another party that can control the relevant asset or infrastructure. Central platforms might restrict accounts or block withdrawals. But assets controlled directly through private keys don't come with a universal "undo" mechanism.
Public chains make transactions observable, which helps investigators understand where funds went and which services may have received them. Still, the chain doesn't automatically make every wallet identifiable. Analysts infer relationships from patterns and supporting information, then update their assessments as new transactions occur. That can support investigations and coordination, but it isn't the same as a court ruling - or a guarantee that someone can take control of the assets.
What a credible recovery update should clarify
When an exchange reports frozen funds, it should ideally spell out the amount, the asset types, the networks involved, and whether those assets are in the company's control or just under monitoring. It also matters whether funds are temporarily restricted, legally seized, or returned to affected users.
Without those distinctions, a headline number can blur multiple stages of incident response.
Binance's pledge to cover losses addresses a separate point: the exchange's commitment to make users whole. It doesn't, by itself, prove that all stolen assets were recovered. Reimbursement and recovery can follow different timelines, and one can happen without the other.
For users and institutions, the practical test isn't just whether a dashboard shows a lot of frozen assets. The real question is whether the exchange explains what's secured, what remains exposed, how losses will be handled, and what investigators can verify. Specific, auditable updates are more useful than one broad total.
What should investors and institutions take from the comparison?
This story is a reminder that on-chain visibility and institutional custody create different kinds of risk. A corporate treasury is typically held as a strategic or operational asset under company controls. Crypto attributed to attackers is evidence of a security incident - and a potential liability for the exchange, its users, and the broader ecosystem.
For companies that hold digital assets, the lesson isn't just "keep balances small." Treasury size is a business choice. What matters just as much are the controls around signing, authorization, and monitoring - because those controls determine how safely the balance can actually be used. A larger treasury with strong, tested controls may be more resilient than a smaller one with weak access management and unclear approvals.
The breach also shows why response plans can't focus only on Bitcoin. The reported theft crossed nine blockchains and involved token swaps. If an organization monitors just one chain, it may miss movements elsewhere - or fail to coordinate quickly with services that can restrict deposits and withdrawals.
A practical incident-readiness checklist
Organizations that custody or manage substantial crypto assets should be able to answer these questions before an incident:
- Who can authorize a transaction? Document key holders, approval thresholds, and emergency procedures. Test whether the controls hold up under pressure.
- How are unusual movements detected? Monitor transactions across relevant networks and define escalation thresholds that separate routine activity from anomalous flows.
- Who coordinates external response? Keep clear contacts and responsibilities for analytics providers, exchanges, legal counsel, and law enforcement.
- How are customer assets separated and reported? Keep corporate holdings distinct from customer assets, both operationally and in public disclosures.
- What does recovery mean in your reporting? Separate traced, frozen, seized, and returned assets so users understand the real status.
None of this guarantees a breach won't happen. The point is to reduce the chance that one compromised component can move funds unchecked - and to shorten the time between detection and coordinated action. That's where operational design can make a measurable difference.
Conclusion
The attackers' reported 18,270 BTC balance exceeded Coinbase's disclosed corporate Bitcoin holdings by 199 BTC, and their attributed Ether balance also topped a listed corporate treasury. Those comparisons underline the scale of the incident - but the numbers need context: they're snapshots, Coinbase's figure excludes customer assets, and tracing alone doesn't guarantee recovery.
For institutions, the takeaway is to treat custody, monitoring, and incident response as one system. Look beyond what a treasury holds. Focus on who can move it, how quickly unusual activity gets detected, and how clearly affected users will be informed once the controls are tested.