How Coinbase protects customer assets
TL;DR: Coinbase was not impacted by Binance's reported hot wallet incident. We keep over 99% of customer assets in cold storage today, and rebalance funds in and out of our hot wallets based on customer deposits and withdrawals demand. Transfers are protected by layers of controls, including distributed keys, withdrawal limits, anomaly detection and kill switches that can halt signing. Customer assets are held 1:1, remain customer property, and are not lent or used unless customers instruct us to. The advancement of artificial intelligence capabilities is rapidly changing the security landscape, and, in response, Coinbase is continuing to invest in best in class security innovation.
Binance’s reported hot wallet incident has understandably left customers asking how Coinbase protects customer assets from something similar happening here. Coinbase was not impacted and our systems and customer funds remain unaffected. This post explains at a high level how Coinbase’s institutional-grade, advanced, layered protections work, and how we keep customer assets safe across all our product surfaces and customer types.
Keeping most assets offline
Coinbase uses two kinds of storage. Our hot wallets store a small percentage of assets so that they are readily available if customers want to withdraw or use them outside of Coinbase, while over 99% of assets today stay in our cold wallets. At Coinbase, hot wallet balances are actively managed and closely monitored by a combination of human personnel, services, and cryptographic systems, so balances stay available as demand changes. We continuously rebalance excess assets to cold storage. Our dedicated Custody vault product assets, the same system that protects our institutional custody, are 100% cold and onchain segregated.
Applying protections to how assets move
Securely storing a wallet is only one part of custody, but wallet transactions also need to be securely verified. For both hot and cold wallets, Coinbase uses layers of controls to help verify that fund movements match their intended purpose. Some of these include:
Distributed key protection: In our cold custody flows, for all customer assets, wallet private keys are split into pieces, and the full wallet private key is never reconstructed in full, even during signing. In our hot flows, no single individual has standing production access to our wallet signing service and any change to the production service requires multiple personnel to be involved. No single point of failure exists in hot or cold wallets, so stealing a laptop, breaking into a server, or one bad actor inside the company cannot sign or reconstruct a wallet private key.
Rate limits and anomaly detection: We set strict limits on the speed at which assets can be transferred from cold wallets to refill hot wallets to serve our customers’ trading needs. When withdrawal volumes trigger alarms or something looks off for a particular account, wallet, asset, or network, our wallet operations team investigates the suspicious activity before a transaction can proceed. A spike can be legitimate, like a busy market day, or a sign that something is wrong. Until someone confirms the activity is normal, the limits stop unusual volume of assets from being transferred from cold to the hot wallets.
Kill switches: We can halt some or all fund movements the moment something looks wrong. Some of these stops are cryptographic: the keys used for signing are taken offline entirely, so no system, compromised or otherwise, can sign until we deliberately restore access. We only restore access after a review confirms the affected systems are intact, the cause is understood, and vault operations are safe to resume.
We also apply core security principles throughout our environment to mitigate the risk that a single malicious actor could unilaterally perform a sensitive function. These controls include:
Limit standing access: we remove standing access to production services where feasible, and enforce secure just-in-time access so that when someone does have to access a production service, they are limited in the amount of time they can do so.
Enforce consensus: applying a code commit to change something in production, getting permissioned to a new access role, and many other activities require either software or cryptographic based consensus and multi-factor authentication to ensure a single user cannot act unilaterally.
Designated personnel for elevated access: highly sensitive roles that can access production service fund flows are designated as such, with personnel going through enhanced background checks and being subject to increased monitoring.
Limit impact of phishing attempts: we assume employees will be targeted by phishing, so alongside our employee training to avoid phishing, our controls are built so a stolen password, session or device can't be used on its own. Sign-in uses phishing-resistant authentication, sensitive actions require independent verification and multiple approvals. Continuous monitoring alerts unusual activity on employee accounts to our global security operations center.
Most trusted exchange with customer assets held 1:1
Assets held at Coinbase are held 1:1 and remain the customer’s property. Coinbase does not lend or use those assets unless customers instruct us to. Our records track customer holdings separately from company assets.
Coinbase is a U.S. based, publicly traded S&P 500 company, our financials are subject to quarterly external auditor review, and we also file annual audited financial statements with the SEC. We are a globally regulated company with 80+ licenses. As of September 30, 2026, Coinbase reported $8.6 billion in cash and cash equivalents, $2.2 billion in crypto assets held for investment, and $377 billion in assets on platform.
An industry-leading security team
Coinbase is held to the standards of the largest financial institutions. Our U.S. custodian, Coinbase Custody Trust Company, is a fiduciary under New York law and a qualified custodian regulated by the New York Department of Financial Services, the same regulator that oversees New York's banks. In Europe, Coinbase is authorized under MiCA and supervised by Luxembourg's CSSF, which lets us serve customers across the EU under one European regulatory framework. We were also one of the first crypto custodians to complete SOC 1 Type II and SOC 2 Type II examinations, which test whether our controls hold up in practice, not just on paper.
Our Chief Security Officer, Jeff Lunglhofer, previously served as Chief Information Security Officer at BNY. He leads a team of security engineers, cryptographers, threat intelligence analysts and investigators, with backgrounds in financial services, national security and law enforcement, who work full time on protecting customer assets and the systems that hold them.
A continuing responsibility
Our responsibility is to keep improving safeguards and continuously monitor for threats so Coinbase can be the best place for customers to grow, use and move their money.
The advancement of artificial intelligence capabilities is rapidly changing the security landscape, and, in response, Coinbase will continue to invest in best in class security innovation. Security will always be our top priority as we maintain our brand as “the most trusted”.
Footnote: For additional information, please refer to our quarterly report on Form 10-Q for the quarter ended September 30, 2026 filed with the SEC on October 29, 2026, as well as other filings we make with the SEC.
