AnswersPublished23 sources
What did Coinbase say on Nov. 4 about the safety of its systems and customer funds after Binance’s Oct. 29 hack, and how do its self reported, independently unverified claim that more than 99% of customer assets are held offline, limited hot wallet balances and routine transfers
4, Coinbase said it had not been affected by Binance’s Oct. 29 breach and that its systems and customer funds remained safe.
Published byImages generated with GPT Image 2
Research answer
Key takeaways
- 4, Coinbase said it had not been affected by Binance’s Oct.
- 29 breach and that its systems and customer funds remained safe.
- It presented its custody safeguards as reassurance—not independent proof that a comparable attack could never succeed.
- [15] Coinbase’s assurances Offline custody: Coinbase said more than 99% of customer assets were held in cold storage; reporting also described segregated assets and multiparty computation key protection.
AI Prompt
openai.comCreate a landscape editorial hero image for this Studio Global article: What did Coinbase say on Nov. 4 about the safety of its systems and customer funds after Binance’s Oct. 29 hack, and how do its self reporte. Article summary: 4, Coinbase said it had not been affected by Binance’s Oct.. Topic tags: general web, ai, automation, workflow, security. Style: premium digital editorial illustration, source-backed research mood, clean composition, high detail, modern web publication hero. Use reference image context only for broad subject, composition, and topical grounding; do not copy the exact image. Avoid: logos, brand marks, copyrighted characters, real person likenesses, fake screenshots, UI text, readable text, watermarks, charts with fake numbers, clickbait thumbnails, icons, and tiny thumbnail layouts. Make it useful as an illustrative visual, not as factual evidence.
On Nov. 4, Coinbase said it had not been affected by Binance’s Oct. 29 breach and that its systems and customer funds remained safe. It presented its custody safeguards as reassurance—not independent proof that a comparable attack could never succeed. 15
Coinbase’s assurances
- Offline custody: Coinbase said more than 99% of customer assets were held in cold storage; reporting also described segregated assets and multiparty-computation key protection. The available evidence does not independently verify that percentage or the effectiveness of those controls.
4
5
- Signing and withdrawal controls: Available reporting supports Coinbase’s emphasis on distributed signing keys, withdrawal restrictions, emergency shutdowns and multi-person approval controls.
14
15 However, the supplied excerpts are insufficient to verify every detail in the question—particularly routine cold-storage transfers, keys never being reconstructed, the precise production-signing controls, unusual-activity monitoring, lending restrictions and AI-related investment.
- Ownership and backing: A social-media summary reported Coinbase’s assertion that customer assets remained backed 1:1 and segregated from corporate funds; that is weaker evidence than a directly inspected company disclosure or independent audit.
54 Backing and segregation address financial protection, but do not themselves establish that withdrawal authorization is secure.
How Binance differed
- Scale and containment: Binance’s Nov. 3 initial-response update put affected assets at approximately $6.34 billion and frozen or intercepted assets at approximately $2.85 billion, subject to reconciliation and market prices.
8 Other reported freeze estimates ranged from roughly $2.7 billion to $3 billion, so these should be treated as dated estimates rather than contradictory final totals.
3
- Attack path: Reporting described fake recruitment interviews delivering malware, an initially identified compromised DevOps laptop, and exploitation of an internal AI tool to extend access.
12
6 Binance’s reported explanation was that attackers manipulated withdrawal approvals rather than stealing private keys; the available excerpts do not establish the precise Ethereum-authorization mechanism.
- Attribution: The FBI attributed the theft of more than $6 billion to North Korea; security reporting identified the group as TraderTraitor.
1
- Loss coverage and reopening: Binance pledged to use company reserves to cover the theft, and reporting said it had replenished approximately 98% of affected assets by Nov. 4.
10
2
- Important gaps: Insufficient evidence in the supplied excerpts to verify the exact phased reopening, the distinction between corporate and customer assets initially stolen, proof-of-reserves expansion from 10 to 44 tokens, remaining hacker-controlled balances, automated laundering, or specific token-price movements. Replacement of assets should not be confused with recovery from the hackers.
What this reveals
- Cold storage is only one layer. The crucial comparison is between protecting keys and protecting the instructions those keys authorize: Binance’s reported approval-system compromise shows why keeping keys secure does not necessarily prevent unauthorized transfers.
- South Korea: Available reporting indicates consideration of stronger cold-storage requirements, but the supplied evidence does not verify the stated 80% requirement or the exact call for stronger cold-wallet and withdrawal safeguards.
- Coinbase’s 2025 incident: Insufficient evidence here to verify the support-agent bribery, customer-data exposure or estimated costs of up to $400 million. If those details are established separately, the relevant distinction is that protecting custody keys does not also protect customer information or prevent impersonation scams.
The supported conclusion is narrower than “Coinbase is immune”: it said it was unaffected and described layered safeguards, while Binance’s reported breach illustrates the importance of securing the entire authorization process, not just private keys. 15
4
5
Studio Global AI
Continue your research
This page includes a source-backed answer you can continue inside Studio Global.
People also ask
What is the short answer to "What did Coinbase say on Nov. 4 about the safety of its systems and customer funds after Binance’s Oct. 29 hack, and how do its self reported, independently unverified claim that more than 99% of customer assets are held offline, limited hot wallet balances and routine transfers"?
4, Coinbase said it had not been affected by Binance’s Oct.
What are the key points to validate first?
4, Coinbase said it had not been affected by Binance’s Oct. 29 breach and that its systems and customer funds remained safe.
What should I do next in practice?
It presented its custody safeguards as reassurance—not independent proof that a comparable attack could never succeed.
Sources