Coinbase Says 99% of Customer Assets Sit in Cold Storage After Binance Breach

Coinbase stated on November 4 that it was not affected by the reported Binance hot-wallet breach and that more than 99% of customer assets are held in cold storage. The disclosure, published in an official post on the Coinbase blog, laid out the exchange's controls around key signing, withdrawal limits and anomaly detection.

The statement arrives as industry participants investigate what sources describe as a multi-billion-dollar exploit at Binance. Coinbase's response doubles as a public test of how custodians should explain security architecture after a peer suffers a major incident.

What did Coinbase disclose?

The exchange described four categories of protection:

• More than 99% of customer assets held in cold storage, keeping signing authority away from internet-connected systems.
• Distributed signing keys, designed so no single compromised system can authorize a large movement of funds.
• Withdrawal limits and anomaly detection that add layers of defense and potentially buy time when a transaction looks unusual.
• Emergency controls capable of halting transaction signing during an incident.

Hot wallets remain necessary for routine withdrawals, which makes the balance between operational liquidity and offline custody a core custodial trade-off. Coinbase framed its percentage as a statement of current practice, not a universal guarantee against every category of risk.

Why cold storage is not the whole answer

Coinbase's own framing concedes the limits of a single headline number. Account takeover, internal controls, fraud, software defects and legal restrictions are separate risk categories that cold storage does not address. The exchange wrote that a security system is strongest when the organization explains the entire chain of access rather than relying on one impressive percentage.

Distributed keys, likewise, only prevent single points of failure if the policy governing those keys is implemented correctly. Limits and monitoring add depth but require rehearsed incident procedures to be effective.

The disclosure period has also pulled other operational controls into view. Stablecoin issuers have described the actions available to them once assets leave a compromised platform, and in decentralized finance, Aave restricted new tBTC supply and borrowing after a mint-and-redeem pause — a move that contained further exposure during an active incident. Custody defenses and downstream tracing are connected but distinct: one aims to stop unauthorized signing, the other to limit damage after funds move.

What should exchange customers ask?

The episode sharpens the due-diligence questions users can put to any custodian:

• Are balances fully backed, and what proportion sits in internet-connected wallets?
• How are withdrawals approved, and who holds signing authority?
• Are controls independently assessed?
• How does the company communicate when access is interrupted?
• What is the difference between assets held by a platform and tokens in a wallet whose private keys the customer personally controls?

Coinbase's statement offered concrete details rather than a bare assertion of security. Those claims now face assessment against future audits, incident disclosures and actual operational performance — the measure the company itself set for judging custodial credibility. The Binance investigation will keep custody design at the center of the exchange risk story, rather than in the small print beneath a trading app, for as long as the reported losses remain unresolved.