NEWS
Coinbase’s 99% Cold Storage Claim Misses the Signing Attack
Coinbase says more than 99% of customer crypto sits offline after Binance’s $6.34 billion theft, yet that attack captured a signing service, not keys.
Coinbase told customers on November 4 that more than 99% of their crypto sits in cold storage, six days after Binance lost $6.34 billion. The U.S. exchange said it was not touched by the theft and that customer assets are held one-for-one, are not lent, and remain customer property.
The thieves who hit Binance did not steal private keys. They captured an internal wallet signing service after a months-long campaign that started with a poisoned software install and a fake job interview, then made hot wallets sign transfers the exchange had not approved.
The More Than 99% Offline Claim From Coinbase
Coinbase posted the reassurance on a Wednesday afternoon, calling secure custody daily work rather than a one-time badge. The company said that means 1:1 backing, more than 99% of funds in offline cold storage, audited financials, and key splits with no single points of failure.
Users come to Coinbase to keep their money secure. We make sure that stays true.
Secure custody is daily work for us, not a one-time achievement.
That means 1:1 backing, >99% of funds in offline cold storage today, audited financials, key splits, no single points of failure and…
— Coinbase 🛡️ (@coinbase) November 4, 2026
Hot wallets still exist. Coinbase said they hold a small share so withdrawals can clear, and that excess balances are swept back offline. Private keys for cold wallets are split and never fully put back together, even while a transaction is signed, and no single employee has standing access to the hot-wallet signing service.
HOW COINBASE SAYS FUNDS MOVE
- Cold share: More than 99% of customer assets sit in wallets that are not on the internet.
- Hot remainder: A small online balance pays withdrawals, then surplus is sent back offline.
- Key splits: Cold-wallet private keys are broken into pieces and never rebuilt in full during signing.
- Rate limits: Caps restrict how fast coins can move from cold wallets into hot ones.
- Alarms: Unusual withdrawal spikes are held for staff review before they go out.
- Kill switches: Signing keys can be taken offline to halt fund movement.
Those extra controls matter more than the headline percentage, because the October 29 theft did not begin with a key sitting on a networked machine. Coinbase also said a stolen password, session, or device is not enough on its own, and that sensitive actions need more than one person’s approval, on the premise that staff will be phished.
The standing custody page is older than the Wednesday note and still does the technical work. Coinbase says it uses secure multiparty computation so signing keys are never in any single place at one time, each party holds a shard that is useless alone, and signing happens without gathering those shards. Each participant is also supposed to check the transaction against policy, so a stolen fragment should not be enough to misuse a key. The Wednesday post did not attach an outside exam to the more than 99% figure itself.
The Binance Thieves Never Needed a Private Key
Binance’s own initial findings, published November 3, said about $6.34 billion of digital assets were affected on October 29. The attacker used unauthorized access to an internal wallet signing service to start transactions outside the normal withdrawal path. Users, Binance said, will not bear the financial hit; 98% of the impacted tokens had been refilled as of October 31, and roughly $2.85 billion has been frozen or intercepted, subject to reconciliation and price moves.
A Tampered Install in June
The campaign was not a single night. In June, an engineer downloaded a tampered Homebrew install while setting up an AI coding tool. Binance said it caught that machine, replaced the device, and rotated credentials, but the wallet team had already been exposed. In September, a fake recruiter on a job platform ran video interviews and sent an assignment repository that carried zero-day malware the endpoint tools did not flag.
On October 20, the attacker used an internal AI tool as a springboard to reach a container deployment token. On October 29, between 17:15 and 19:56 UTC, they logged into a third engineer’s computer, deployed a container with the stolen credentials, and triggered the drain. Binance said it had blocked 57 suspected North Korea-linked threats this year. The FBI, in an October 31 alert, said North Korea was responsible for the theft of more than $6 billion in virtual assets from Binance on or about October 29, and named that activity TraderTraitor.
The FBI is releasing information advising the Democratic People’s Republic of Korea (North Korea) was responsible for the theft of more than $6 billion USD in virtual assets from cryptocurrency exchange, Binance, on or about October 29, 2026. The FBI refers to this specific North Korean malicious cyber activity as “TraderTraitor.”
FBI San Diego, official alert, October 31, 2026
That FBI floor and Binance’s $6.34 billion accounting describe the same night. Binance is the figure this piece uses for what left the platform.
Fifty Signing Transactions on Ethereum
The first burst was short. Between 20:05 and 20:09 UTC, five hot wallets sent 233.46 million XRP to an attacker-controlled address, a four-minute window. Solana and Optimism wallets then sent about 970,500 SOL and 44.2 million OP, and an 18,270 BTC transfer followed. The attacker next used Ethereum’s EIP-7702 feature, which lets a wallet hand some of its powers to a contract, and locked in that handoff with 50 signing transactions so a contract they controlled gained partial rights over a hot wallet.
Turning off withdrawals and shutting hot-wallet services did not wipe those on-chain authorizations. Because the wallet used multiparty computation, there was no single private key to revoke, and a special procedure took extra time. The last unauthorized transfer, 2,961.9 ETH, finalized at 23:56 UTC. Binance cleared the EIP-7702 delegation from its Binance14 hot wallet at 00:10 UTC on October 30. The same family of split-key math Coinbase now advertises is what slowed Binance’s kill once the signer was already captured.
THE PATH INTO BINANCE’S SIGNER
- June 2026: An engineer installs a tampered Homebrew package while setting up an AI coding tool; Binance replaces the device but the wallet team is already exposed.
- September 2026: A fake recruiter runs video interviews and delivers an assignment repo with zero-day malware that endpoint tools miss.
- October 20, 2026: The attacker uses an internal AI tool to reach a container deployment token.
- October 29, 2026, 17:15-19:56 UTC: A container is deployed from a third engineer’s computer and the drain is armed.
- October 29, 2026, 20:05-20:09 UTC: Five hot wallets send 233.46 million XRP; SOL, OP, and 18,270 BTC follow.
- October 29, 2026, 23:56 UTC: The last unauthorized transfer, 2,961.9 ETH, finalizes; the EIP-7702 code is cleared at 00:10 UTC on October 30.
Binance said it rebuilt the affected wallet system and the internal AI tool, replaced devices, retired related credentials, scanned employee machines, and expanded AI-based anomaly detection. It is commissioning an independent review. It also said the incident should not have happened.
$1.5 Billion Left a Cold Wallet at Bybit
If offline storage were the whole defense, the February 2025 Bybit theft would not exist. About $1.5 billion left an Ethereum cold wallet after attackers altered the interface Bybit’s human signers used, so those signers approved a transfer they did not intend. Private keys were not exported. The signatures were genuine. The FBI later tied that theft to the same TraderTraitor unit it named after October 29.
Bybit’s failure is the hard case against Coinbase’s lead statistic. The coins were already cold. Several people had to approve the move. Every one of them saw the same false screen. Cold storage did not get a vote once the approval path was poisoned. Coinbase’s Wednesday note still opens on the share of assets that are offline, which is the metric that would have looked fine at Bybit until the moment the cold wallet signed.
Bitget’s Signer Approved the Forged Transfers
Bitget’s September 24, 2026 theft sits between those two poles. Attackers got into a backend system tied to the wallet stack, spoofed transaction data, and fed forged withdrawal orders into the authorization process. Hot and warm wallets then paid the attacker. Bitget said its private keys were not compromised and its cold wallets were not touched. TRM Labs, which published an on-chain account of that night, put the same failure next to Bybit: the attacker changed what the approver saw or received, rather than stealing the secret that unlocks the vault.
On Bitget, there was no human screen to fake. Automated signing ran on forged backend data and did what it was built to do. Customer payouts and the thefts sat in the same queue. The lesson is mechanical. If the service that tells a wallet what to sign is captured, the wallet will sign, whether the coins behind it are labeled hot, warm, or cold.
THREE THEFTS, ONE FAILURE CLASS
| Exchange | Date | Amount | Wallet hit | Keys stolen |
|---|---|---|---|---|
| Bybit | February 2025 | $1.5 billion | Cold | No |
| Bitget | September 24, 2026 | $387.5 million | Hot and warm | No |
| Binance | October 29, 2026 | $6.34 billion | Hot | No |
Coinbase uses MPC too. So did Binance’s affected hot wallet. Split keys stop an attacker who needs a complete secret in one place. They do not, on their own, stop an attacker who can make the existing signer approve a transfer it should have refused. That is the gap the more than 99% line does not close.
Coinbase’s 2025 Breach Ran as High as $400 Million
Coinbase has already been hit through people, not through a hot-wallet key. In May 2025 it said cyber criminals bribed and recruited a group of rogue overseas support agents to copy customer data from support tools, covering less than 1% of monthly transacting users. No passwords, private keys, or funds were taken from wallets. The criminals then impersonated Coinbase and tried to trick customers into sending coins, and they demanded a $20 million ransom that Coinbase refused, posting a $20 million bounty instead.
A filing put remediation and voluntary reimbursements in a range of $180 million to $400 million. Coinbase said it would repay customers who were fooled into sending funds, and that Prime accounts and customer hot or cold wallets were not accessed. That incident is the company’s documented failure mode: insiders with the wrong kind of access, cash on the table, and a long dwell time before disclosure. It is also closer to Binance’s fake-interview path than to a 2014-style key theft.
A card that spends against an exchange balance still has to draw on whatever the platform keeps hot enough to pay. The Wednesday post does not say how large that working balance is, only that it is the minority share. Customers are being asked to take Coinbase’s word on the split.
What the Kill Switches and Key Splits Cover
Read past the percentage and Coinbase is describing a signing-path defense. Rate limits on cold-to-hot refills, alarms that pause odd withdrawal spikes, a rule that no one person holds standing production access to the hot signing service, and kill switches that take keys offline are the controls that map to October 29. They are also the controls that have to work in minutes, because Binance’s first XRP burst was over in four.
MPC is the other advertised layer. Coinbase’s help page says each participant checks a transaction against policy, so a subset of machines should not be enough to extract key material or bypass misuse protections. Binance’s night showed the other edge of that design. Once authorizations were on-chain, the lack of a single key to revoke became a delay, not a brake. A kill switch that takes signing keys offline helps only if it fires before 50 EIP-7702 transactions have already locked in a delegation.
Coinbase Custody Trust Company is a New York limited-purpose trust, a qualified custodian, and a fiduciary under New York banking law. It keeps SOC 1 Type II and SOC 2 Type II exams by Deloitte & Touche, and it says key generation and cold-storage technology come from more than 12 years of in-house work. Those exams test controls and process. They are not a public, independent count of how much customer crypto is offline on a given day. The Wednesday post did not supply that count from anyone but Coinbase.
The $377 Billion Still Has to Be Signed
The book behind the promise is large. With its third-quarter results, Coinbase reported about $377 billion of assets on the platform as of September 30, $8.6 billion in cash and cash equivalents, and $2.2 billion in corporate crypto, kept on separate books from customer property. Hosted Coinbase.com accounts are the ones covered by the custody claims. Self-custody users still hold their own keys.
COINBASE’S SEPTEMBER 30 SNAPSHOT
- Assets on platform: About $377 billion at period end, customer property on Coinbase’s telling.
- Company cash: $8.6 billion in cash and cash equivalents.
- Corporate crypto: $2.2 billion, booked apart from customer assets.
- Offline claim: More than 99% of customer assets in cold storage as of November 4, per Coinbase.
Artificial intelligence sits in both stories. Binance’s attacker used an internal AI tool as a ladder between engineers. Coinbase said it will keep spending on security as those tools change how staff, systems, and customers get targeted. That is the live surface. The coins that pay withdrawals still need a signer, and the signer still sits behind people, laptops, deployment tokens, and policy checks. Cold storage keeps the rest of the pile off the internet. It does not decide what that signer will approve when someone who should not have reached it already has.
Disclaimer: This article is news reporting and analysis of public company statements, incident findings, and on-chain research. It is informational only and is not investment, legal, or security advice, and it is not a recommendation to keep, move, or withdraw crypto on any exchange or wallet. Readers who need advice on custody, account security, or the legal status of assets should consult a qualified financial adviser, attorney, or independent security professional before acting. Figures and incident statuses reflect the cited company filings, blogs, and alerts as dated in the piece and can change as investigations, freezes, and refills continue.
-
BUSINESS5 months agoAramco Crash Kills 14 Two Days After Oil Restart
-
NEWS6 months agoSalah Captained Egypt to Their First World Cup Win
-
GAMING2 months agoZelda’s 40th Switch 2 Ships Without a Zelda Game
-
NEWS3 months agoApple Labor Day Deals Hide June’s Memory Price Hike
-
NEWS4 months agoEl Niño Puts Israel’s Needed Winter Rain on a Flood Clock
-
GAMING2 months agoPalworld 1.0.4 Adds Palpedia Search After the 1.0 Launch
-
NEWS4 months agoSaudi Visa Routes Split Nigerian Travelers Into Two Speeds
-
BUSINESS9 months agoBAE’s 60-Year Saudi Franchise Now Runs Through Taif
