How a five-year-old build flag drained $116 million from bitcoin’s most trusted hardware wallet

cryptonews08-06 17:06

A single line of firmware shipped in March 2021 told every Coldcard hardware wallet to skip its dedicated randomness chip. For five years nobody noticed. Then an attacker brute-forced the weak seeds ...

Source Link

Disclaimer: Investing carries risk. This is not financial advice. The above content should not be regarded as an offer, recommendation, or solicitation on acquiring or disposing of any financial products, any associated discussions, comments, or posts by author or other users should not be considered as such either. It is solely for general information purpose only, which does not consider your own investment objectives, financial situations or needs. TTM assumes no responsibility or warranty for the accuracy and completeness of the information, investors should do their own research and may seek professional advice before investing.

Comments

We need your insight to fill this gap

Leave a comment

{"i18n":{"language":"en_US"},"isChannel":false,"data":{"share":"https://ttm.financial/m/news/2657689746?lang=en_US&edition=fundamental","thumbnail":"","is_english":true,"pubTime":"2026-08-06 17:06","share_image_url":"https://static.laohu8.com/e9f99090a1c2ed51c021029395664489","id":"2657689746","market":"nz","top_or_hot":-1,"title":"How a five-year-old build flag drained $116 million from bitcoin’s most trusted hardware wallet","media":"cryptonews","content":"<div>\n<p>A single line of firmware shipped in March 2021 told every Coldcard hardware wallet to skip its dedicated randomness chip. For five years nobody noticed. Then an attacker brute-forced the weak seeds ...</p>\n\n<a href=\"https://crypto.news/coldcard-hack-bitcoin-self-custody-entropy/\">Source Link</a>\n\n</div>\n","source":"crypto_news_highlight","html":"<!DOCTYPE html>\n<html>\n<head>\n<meta http-equiv=\"Content-Type\" content=\"text/html; charset=utf-8\" />\n<meta name=\"viewport\" content=\"width=device-width,initial-scale=1.0,minimum-scale=1.0,maximum-scale=1.0,user-scalable=no\"/>\n<meta name=\"format-detection\" content=\"telephone=no,email=no,address=no\" />\n<title>How a five-year-old build flag drained $116 million from bitcoin’s most trusted hardware wallet</title>\n<style type=\"text/css\">\na,abbr,acronym,address,applet,article,aside,audio,b,big,blockquote,body,canvas,caption,center,cite,code,dd,del,details,dfn,div,dl,dt,\nem,embed,fieldset,figcaption,figure,footer,form,h1,h2,h3,h4,h5,h6,header,hgroup,html,i,iframe,img,ins,kbd,label,legend,li,mark,menu,nav,\nobject,ol,output,p,pre,q,ruby,s,samp,section,small,span,strike,strong,sub,summary,sup,table,tbody,td,tfoot,th,thead,time,tr,tt,u,ul,var,video{ font:inherit;margin:0;padding:0;vertical-align:baseline;border:0 }\nbody{ font-size:16px; line-height:1.5; color:#999; background:transparent; }\n.wrapper{ overflow:hidden;word-break:break-all;padding:10px; }\nh1,h2{ font-weight:normal; line-height:1.35; margin-bottom:.6em; }\nh3,h4,h5,h6{ line-height:1.35; margin-bottom:1em; }\nh1{ font-size:24px; }\nh2{ font-size:20px; }\nh3{ font-size:18px; }\nh4{ font-size:16px; }\nh5{ font-size:14px; }\nh6{ font-size:12px; }\np,ul,ol,blockquote,dl,table{ margin:1.2em 0; }\nul,ol{ margin-left:2em; }\nul{ list-style:disc; }\nol{ list-style:decimal; }\nli,li p{ margin:10px 0;}\nimg{ max-width:100%;display:block;margin:0 auto 1em; }\nblockquote{ color:#B5B2B1; border-left:3px solid #aaa; padding:1em; }\nstrong,b{font-weight:bold;}\nem,i{font-style:italic;}\ntable{ width:100%;border-collapse:collapse;border-spacing:1px;margin:1em 0;font-size:.9em; }\nth,td{ padding:5px;text-align:left;border:1px solid #aaa; }\nth{ font-weight:bold;background:#5d5d5d; }\n.symbol-link{font-weight:bold;}\n/* header{ border-bottom:1px solid #494756; } */\n.title{ margin:0 0 8px;line-height:1.3;color:#ddd; }\n.meta {color:#5e5c6d;font-size:13px;margin:0 0 .5em; }\na{text-decoration:none; color:#2a4b87;}\n.meta .head { display: inline-block; overflow: hidden}\n.head .h-thumb { width: 30px; height: 30px; margin: 0; padding: 0; border-radius: 50%; float: left;}\n.head .h-content { margin: 0; padding: 0 0 0 9px; float: left;}\n.head .h-name {font-size: 13px; color: #eee; margin: 0;}\n.head .h-time {font-size: 11px; color: #7E829C; margin: 0;line-height: 11px;}\n.small {font-size: 12.5px; display: inline-block; transform: scale(0.9); -webkit-transform: scale(0.9); transform-origin: left; -webkit-transform-origin: left;}\n.smaller {font-size: 12.5px; display: inline-block; transform: scale(0.8); -webkit-transform: scale(0.8); transform-origin: left; -webkit-transform-origin: left;}\n.bt-text {font-size: 12px;margin: 1.5em 0 0 0}\n.bt-text p {margin: 0}\n</style>\n</head>\n<body>\n<div class=\"wrapper\">\n<header>\n<h2 class=\"title\">\nHow a five-year-old build flag drained $116 million from bitcoin’s most trusted hardware wallet\n</h2>\n\n<h4 class=\"meta\">\n\n\n2026-08-06 17:06 GMT+8&nbsp;&nbsp;&nbsp;<a href=https://crypto.news/coldcard-hack-bitcoin-self-custody-entropy/><strong>cryptonews</strong></a>\n\n\n</h4>\n\n</header>\n<article>\n<div>\n<p>A single line of firmware shipped in March 2021 told every Coldcard hardware wallet to skip its dedicated randomness chip. For five years nobody noticed. Then an attacker brute-forced the weak seeds ...</p>\n\n<a href=\"https://crypto.news/coldcard-hack-bitcoin-self-custody-entropy/\">Source Link</a>\n\n</div>\n\n\n</article>\n</div>\n</body>\n</html>\n","isBrief":false,"type":0,"news_type":1,"symbol":"YBIT","symbol_name":"YieldMax Bitcoin Option Income ETF","start_time":0,"source_url":"https://crypto.news/coldcard-hack-bitcoin-self-custody-entropy/","article_id":"2657689746","we_media_id":null,"thumbnails":[],"rights":{"source":"crypto_news_highlight","url":"https://crypto.news/coldcard-hack-bitcoin-self-custody-entropy/","rn_cache_url":null,"directOrigin":true},"url":"https://stock-news.laohu8.com/highlight/detail?id=2657689746","pubTimestamp":1786007206,"columns":[],"sourceInfo":{"source_id":"crypto_news_highlight","name":"Crypto News"},"weMediaInfo":null,"summary":"A single line of firmware shipped in March 2021 told every Coldcard hardware wallet to skip its dedicated randomness chip. For five years nobody noticed. Then an attacker brute-forced the weak seeds in 41 minutes, draining 1,816 BTC from more than 5,200 addresses across four attack waves. The incident is the largest hardware wallet exploit in crypto history, and it is forcing the entire bitcoin self-custody model to answer a question it has avoided since inception: who audits the code that generates your keys?“Perhaps the hardest part about this is that I did everything right,” Canadian entrepreneur Jonathan Goodman wrote on X after losing 18.25 BTC, worth approximately C$1.6 million, from a Coldcard stored in a safety deposit box. His post has been viewed more than 7.6 million times. The sentiment captures the core of the crisis: the people who lost money were not careless. They were the most security-conscious bitcoin holders in the ecosystem, and they followed every recommended prac","collect":0,"end_time":0,"defaultTopTitle":"crypto.news","property":[],"viewcount":null,"language":"en","relate_stocks":{"YBIT":"YieldMax Bitcoin Option Income ETF","TXXH":"21Shares 2x Long HYPE ETF","HODL":"比特币ETF-VanEck","MAXI":"比特币期货ETF-Simplify","BTC":"Grayscale Bitcoin Mini Trust","BITB":"比特币ETF-Bitwise","YBTC":"比特币看涨期权ETF-Roundhill","BTCI":"NEOS Bitcoin High Income ETF","LFGY":"YieldMax Crypto Industry and Tech Portfolio Option Income ETF","BITC":"Bitwise Trendwise Bitcoin and Treasuries Rotation Strategy ETF","HECO":"SPDR Galaxy Hedged Digital Asset Ecosystem ETF","BETE":"等权重比特币&以太币期货ETF-ProShares","FBTC":"比特币ETF-Fidelity","BTF":"比特币&以太币期货ETF-CoinShares","BITI":"1倍做空比特币期货ETF-Proshares","BETH":"比特币&以太币期货ETF-ProShares","CBTJ":"Calamos Bitcoin 80 Series Structured Alt Protection ETF - January","MSBT":"Morgan Stanley Bitcoin Trust ETP","BTFX":"比特币期货ETF-CoinShares","BTCL":"T-REX 2X LONG BITCOIN DAILY TARGET ETF","BEGS":"RAREVIEW 2X BULL CRYPTOCURRENCY & PRECIOUS METALS ETF","BTGD":"STKD Bitcoin & Gold ETF","BRRR":"比特币ETF-CoinShares","BTCO":"比特币ETF-Invesco Galaxy","GBTC":"比特币ETF-Grayscale","BITQ":"Bitwise Crypto Industry Innovators ETF","CRPT":"First Trust SkyBridge Crypto Industry and Digital Economy ETF","IBIT":"比特币ETF-iShares","OOQB":"One+One Bitcoin and Ether ETF","BITU":"2倍做多比特币期货ETF-Proshares","GDLC":"Grayscale CoinDesk Crypto 5 ETF","BKCH":"AdvisorShares Sabretooth ETF","BTRN":"比特币期货ETF-Global X","ARKB":"比特币ETF-21Shares","BITW":"Bitwise 10 Crypto Index ETF","WGMI":"比特币矿商ETF-CoinShares","STCE":"Schwab Crypto Thematic ETF","BTCZ":"T-Rex 2X Inverse Bitcoin Daily Target ETF","BITX":"2倍比特币期货ETF-Volatility Shares","MNRS":"GRAYSCALE BITCOIN MINERS ETF","NGHT":"Nicholas Bitcoin and Treasuries AfterDark ETF","ARKY":"ARK 21SHARES ACTIVE BITCOIN ETHEREUM STRATEGY ETF","NCIQ":"HASHDEX NASDAQ CRYPTO INDEX US ETF","DAPP":"VanEck Digital Transformation ETF","SBIT":"2倍做空比特币期货ETF-Proshares"},"translate_title":"五年前的 build flag 如何从比特币最值得信赖的硬件钱包中榨取 1.16 亿美元","themeId":null,"isJumpTheme":false,"ttsUrl":null,"symbols_score_info":{"ARKB":1.5,"BTCI":1.5,"CRPT":1.5,"OOQB":0.9,"BRRR":1.5,"MBTmain":1.5,"XBTmain":0.9,"SBIT":1.5,"BITW":1.5,"ARKY":1.5,"BTCL":1.5,"BTRN":1.5,"BTCO":1.5,"STCE":1.5,"YBTC":1.5,"BEGS":1.5,"CBTJ":1.5,"IBIT":0.9,"BITI":1.5,"GDLC":1.5,"MAXI":1.5,"BTC":0.9,"WGMI":1.5,"DAPP":1.5,"BKCH":1.5,"GBTC":1.5,"BTCZ":1.5,"BITQ":1.5,"BITU":1.5,"FBTC":1.5,"YBIT":1.5,"BTFX":1.5,"LFGY":1.5,"BITX":1.5,"BITB":1.5,"HECO":1.5,"MSBT":1.5,"BITC":1.5,"BETH":1.5,"BTF":1.5,"BTCmain":0.9,"MNRS":1.5,"TXXH":1.5,"BTGD":1.5,"HODL":1.5,"NGHT":1.5,"BETE":1.5,"NCIQ":1.5},"content_text":"A single line of firmware shipped in March 2021 told every Coldcard hardware wallet to skip its dedicated randomness chip. For five years nobody noticed. Then an attacker brute-forced the weak seeds in 41 minutes, draining 1,816 BTC from more than 5,200 addresses across four attack waves. The incident is the largest hardware wallet exploit in crypto history, and it is forcing the entire bitcoin self-custody model to answer a question it has avoided since inception: who audits the code that generates your keys?\n\n\nSummary\n\n\n\nA build configuration error in Coldcard firmware version 4.0.1, shipped in March 2021, routed seed generation to a deterministic software pseudorandom number generator instead of the device’s STM32 hardware random number generator, reducing effective entropy from 128 bits to approximately 40 bits on Mk3 devices and 72 bits on Mk4, Mk5, and Q models.\nAn attacker began sweeping wallets on July 30, 2026, draining 1,082 BTC from 1,196 addresses in 41 minutes during the first wave, with Galaxy Research tracking total confirmed losses of 1,596 BTC across three waves and estimating the figure could reach 2,055 BTC (approximately $130 million) if a suspected fourth wave is verified.\nCoinkite released emergency firmware on July 31 but confirmed that updating does not repair seeds already generated on vulnerable firmware, meaning every affected user must generate a new seed and manually migrate funds to survive.\nThe net transfer of bitcoin from self-custody wallets to exchange addresses has been positive every day since July 31, reversing a two-year outflow trend that began after the FTX collapse, with OKX reporting record exchange inflows in the days following the exploit.\nTRM Labs classified the incident as the third-largest crypto hack of 2026, bringing the year’s total past $1.2 billion across 276 incidents, while roughly 90% of stolen bitcoin remains unmoved at attacker-controlled addresses.\n\n\n\nNobody was phished. No device was stolen. No seed phrase was written on a sticky note. The Coldcard hardware wallet, the device that bitcoin maximalists recommended above all others for cold storage, generated weak private keys for five years because a single build flag told the firmware to skip its dedicated randomness chip. An attacker figured out how to guess the resulting seeds, and on July 30, 2026, began emptying wallets at a pace that left no time to react.\n“Perhaps the hardest part about this is that I did everything right,” Canadian entrepreneur Jonathan Goodman wrote on X after losing 18.25 BTC, worth approximately C$1.6 million, from a Coldcard stored in a safety deposit box. His post has been viewed more than 7.6 million times. The sentiment captures the core of the crisis: the people who lost money were not careless. They were the most security-conscious bitcoin holders in the ecosystem, and they followed every recommended practice except one they could not have known about. The firmware that generated their keys was broken from the day it shipped.\nThe fallout extends far beyond the immediate losses. Bitcoin is flowing back to exchanges for the first time since FTX collapsed. Hardware wallet manufacturers face calls for independent audits of their seed generation code. ARK Invest’s director of digital asset research called the self-custodial hardware space “a disaster.” And Coinkite’s CEO suggested that artificial intelligence found the bug, raising the question of whether every open-source firmware repository is now an attack surface that AI can mine faster than human reviewers can defend.\nThe build flag: how one line of code broke everything\nThe technical failure is simple enough to explain in a single paragraph, which makes it more damaging, not less. Coldcard’s firmware defines a macro called MICROPY_HW_ENABLE_RNG and sets it to zero because Coinkite supplies its own hardware random number generator wrapper. A supporting cryptographic library called libngu checked whether the macro existed. It did not check whether the macro was enabled. Because the macro existed but was set to zero, libngu concluded that hardware randomness was unavailable and fell through to MicroPython’s Yasmarang software fallback. That fallback was initialized from the chip’s unique serial number and timer registers and collected no fresh entropy after initialization.\nThe consequence was a catastrophic reduction in key strength. A 12-word BIP-39 seed phrase is designed to encode 128 bits of entropy, a number so large that brute-forcing it would require more energy than the sun will produce in its lifetime. The Yasmarang fallback, seeded from a chip serial number and timer state, produced approximately 40 bits of effective entropy on the Mk3 and roughly 72 bits on the Mk4, Mk5, and Q. Block’s security research team, which published a detailed technical analysis, set conditional ceilings below 2^40.7 and 2^73.3 and warned that the latter figure is not equivalent to 73-bit cryptographic security.\nForty bits of entropy means approximately one trillion possible seeds. That is a large number by human intuition but a trivial number by computational standards. A modern GPU cluster can enumerate one trillion candidates in hours. The attacker did not need physical access to any device. The attacker did not need to intercept any communication. The attacker needed only to generate candidate seeds, derive their corresponding bitcoin addresses, and compare those addresses against the public blockchain. Every match was a wallet that could be emptied.\nThe flaw shipped in firmware version 4.0.1 in March 2021. It persisted through every subsequent firmware release until the emergency patch on July 31, 2026. Every Coldcard seed generated during that five-year window without the manual dice-roll option is potentially compromised. Coinkite estimates that the dice-roll option, where users physically roll dice at least 50 times and type in the results, bypasses the broken code entirely. The company also says a strong BIP-39 passphrase creates a separate wallet the seed words alone cannot reach. But as Casa CEO Nick Neuman pointed out: “You just cannot ask people to roll dice to be secure with your self-custody. It is a non-starter for 99% of people.”\nThe four waves: anatomy of a $116 million sweep\nThe attack unfolded in distinct waves, each larger than the last, suggesting either a single operator refining their approach or multiple attackers working from the same vulnerability.\nWave one hit on July 30 at approximately 2:14 a.m. UTC. The attacker swept 594 BTC from roughly 500 addresses in 25 minutes, broadcasting transactions at a uniform 30 sat/vB fee rate with no change outputs. Galaxy Research noted that no other bitcoin transactions in the previous 30 days carried the same fee-rate-plus-no-change signature, making the operator identifiable even though they remained anonymous.\n\nNEW: Bloomberg analyst Eric Balchunas highlights ETF fee advantageCrypto ETFs offer 1-3bps access compared with traditional exchange costs pic.twitter.com/GTnjXl91sc— crypto.news (@cryptodotnews) July 27, 2026\n\nWave two followed within 48 hours, lifting the cumulative total to 1,082 BTC from 1,196 addresses. The transaction construction matched Wave one closely enough for Galaxy to assess with high confidence that the same operator was responsible.\n\n\n\n\n\n                Read more:\n            \n\n                Galaxy estimates Coldcard exploit may have stolen up to 2,055 bitcoin            \n\nWave three brought the confirmed total to 1,367 BTC from 4,585 addresses, worth approximately $89 million. Galaxy cautioned that Wave three should not be assumed to involve the same attacker, as the transaction patterns diverged from the first two waves. TRM Labs independently identified differences in transaction construction across waves that hint at multiple operators.\nA suspected fourth wave ran throughout August 4, sweeping roughly 449 BTC from 709 addresses on Galaxy’s revised count. If confirmed, cumulative losses reach approximately 2,055 BTC, worth close to $130 million. Galaxy has reported roughly 600 suspected attacker-controlled addresses to federal investigators, compliance firms, and cybersecurity investigators.\nThe laundering has been minimal. TRM Labs found that most victim funds are pooling at a small number of attacker-controlled addresses with limited onward movement. As of August 4, the only confirmed laundering consisted of a single 64.9 BTC deposit to Wasabi Wallet’s coinjoin service and 200 ETH deposited to Tornado Cash. One opportunist posted an OP_RETURN message on the bitcoin blockchain offering to launder the stolen funds for a 7% fee. The relative inaction suggests the attackers have not yet determined how to move a sum large enough to attract attention wherever it lands.\nThe section a competitor could not write: what 40 bits of entropy actually means\nMost coverage of the Coldcard hack describes the entropy reduction as a technical detail. It is the entire story, and the arithmetic reveals why the attack was inevitable rather than merely possible.\nA 128-bit seed has 2^128 possible values, a number with 39 digits. Brute-forcing that space is not a matter of computing power or patience. It is physically impossible with any technology that obeys the laws of thermodynamics. This is why hardware wallets work at all: the security of a properly generated seed does not depend on the device remaining secret, the firmware remaining uncompromised, or the manufacturer remaining trustworthy. It depends on mathematics.\nA 40-bit seed has 2^40 possible values: 1,099,511,627,776. One trillion. A single NVIDIA H100 GPU can compute roughly 10 billion SHA-256 hashes per second. Deriving a bitcoin address from a candidate seed requires several cryptographic operations beyond a single hash, but the order of magnitude holds. One trillion candidates can be exhausted in minutes to hours on a GPU cluster that costs a few thousand dollars to rent.\nThe Mk4, Mk5, and Q devices had roughly 72 bits of effective entropy. That is better than 40 bits but still catastrophically below 128 bits. Block’s analysis set the search space at approximately four billion possibilities under certain constraints, a number that runs on ordinary hardware. The distinction matters: Mk3 owners face near-certain compromise if their addresses are identified, while later-model owners face a probabilistic threat that depends on how much the attacker knows about their device’s unique ID, boot timing, and prior random number generator calls.\n\n\n\n\n\n                You might also like:\n            \n\n                Coldcard exploit sparks call for independent audits: Kraken CSO            \n\nThe critical insight is that the attacker does not need to know which addresses belong to Coldcard users. Every bitcoin address is public. The attacker generates candidate seeds, derives addresses, and checks them against the entire blockchain. Any match is a confirmed Coldcard wallet with a weak seed. The attack scales linearly with computing power and requires no intelligence about individual victims. Galaxy Research warned that “every vulnerable device will eventually be emptied” because the attacker can work through the entire search space at leisure.\nThis is fundamentally different from a phishing attack, an exchange hack, or a supply chain compromise. Those attacks require targeting specific victims. The Coldcard exploit targets mathematics. Every wallet generated on affected firmware is vulnerable regardless of how carefully the owner stored the device, protected the seed phrase, or followed security best practices. The only defense was an action the manufacturer never told users they needed to take: rolling physical dice.\nThe self-custody reversal: bitcoin flows back to exchanges\nThe Coldcard exploit is producing a behavioral shift that would have been unthinkable 18 months ago. Bitcoin is moving from self-custody wallets back to centralized exchanges, reversing a trend that began when FTX collapsed in November 2022 and accelerated through 2023 and 2024 as hardware wallet sales surged.\nThe net transfer of bitcoin from self-custody wallets to exchange addresses has been positive every day since July 31, according to on-chain flow data. OKX reported record exchange inflows in the days following the exploit. The exchange’s chief compliance officer Jonathan Brockmeier said customer behavior changed “noticeably” as users moved assets away from self-custody.\nThe flow reversal is not limited to panicking retail holders. Institutional allocators who previously cited self-custody as a risk-management advantage are reassessing. Bitcoin ETF inflows reached $211.5 million on August 5, led by BlackRock’s IBIT and Fidelity’s FBTC, suggesting that at least some capital is rotating from direct bitcoin holdings into regulated wrappers that eliminate seed-management risk entirely.\n\n\n\n\n\n                You might also like:\n            \n\n                Coldcard exploit drives record OKX inflows as users rethink self-custody            \n\nBloomberg senior ETF analyst Eric Balchunas argued that spot bitcoin ETFs remove the seed-management problem for investors who want price exposure without operational risk. “An ETF fixes this,” he wrote. On-chain analyst Willy Woo pushed back, arguing that self-custody remains the only path to genuinely sovereign bitcoin ownership and that ETF wrappers introduce counterparty risk that the bitcoin network was designed to eliminate.\nThe data tells a more specific story than either side acknowledges. The addresses moving bitcoin back to exchanges skew toward single-signature wallets holding between 0.5 and 10 BTC, the range most likely to represent individual holders who used a single Coldcard as their primary storage. Multisignature wallets and addresses associated with institutional custodians have shown no comparable movement. The panic is concentrated among the exact user profile the Coldcard was designed for: technically literate individuals who chose self-custody over exchanges and relied on a single hardware device as their sole security layer. The irony is precise. The users who trusted the hardware most are the ones most exposed, while users who distributed trust across multiple devices and key generation methods are unaffected.\nThe tension is real but the framing is incomplete. The Coldcard hack did not expose a flaw in self-custody as a concept. It exposed a flaw in one manufacturer’s implementation of seed generation. Vincent Bouzon, a cybersecurity expert at Ledger, drew the distinction explicitly: “Every wallet ultimately depends on a root secret generated from high-quality entropy. That generation must be anchored in secure hardware, with an architecture that cannot silently downgrade to an untrusted software-based source.” He called the alternatives worse, describing software wallets on non-secure hardware as riskier and centralized exchange custody as “not ownership, it is an IOU.”\nThe AI question: did a model find this bug?\nCoinkite’s response to the exploit included a claim that has divided the security community. CEO Rodolfo Novak, known as NVK, suggested that the attacker used AI to discover the firmware flaw, and that Coinkite’s own AI-assisted code review of the same repository weeks earlier had found nothing.\n“To every other developer: we believe this is a sober reality of the new AI paradigm,” Novak wrote. “AI-assisted code review can now find latent bugs at a speed that is outpacing even the industry’s most seasoned experts.” He added: “If your firmware is open-source or has ever been public, assume it is already being read by attackers and defenders alike.”\n\nJUST IN: Triple-A wallets face active exploit with over 9.7 million dollars drainedSuspicious outflows hit TRON Ethereum Polygon and Arbitrum as funds consolidate into 5,227 $ETH pic.twitter.com/ESqQ7MVuey— crypto.news (@cryptodotnews) July 25, 2026\n\nSecurity researchers have pushed back on this framing. A build flag that disables a hardware random number generator is a human engineering error, they argue, and conventional code review should have caught it years before any language model read the repository. Andrew Lazutkin, chief technology officer at Tangem, drew a different conclusion: “This incident is a good example of why open-source firmware should not automatically be equated with better security.”\nThe AI attribution matters less than the structural question it raises. Whether the attacker used AI, conventional static analysis, or manual review, the result is the same: a bug that sat in plain sight for five years in an open-source repository was found and weaponized. If AI tools can systematically scan firmware repositories for entropy flaws, randomness downgrade paths, and build configuration errors, then every hardware wallet manufacturer with public code faces an expanded attack surface. The question is not whether AI was involved in this specific attack. The question is whether AI makes this class of attack reproducible at scale.\nThe timeline supports the concern regardless of the mechanism. Coldcard’s firmware has been open source since its inception. The MICROPY_HW_ENABLE_RNG macro and its zero assignment were visible in a public GitHub repository for five years. Multiple security researchers, firmware auditors, and the broader Bitcoin development community had access to the code throughout that period. None of them caught the flaw. The Coinspect research group published its Ill Bloom findings on weak PRNG flaws in older software wallets in early July 2026, a separate but thematically identical vulnerability that drained more than $5 million from addresses across Bitcoin, Ethereum, Tron, Rootstock, and Polygon. The clustering of entropy-related exploits within a single month suggests either coordinated research or a shared analytical approach that is surfacing this class of bug faster than it has been found historically.\nThe opposing case at full strength\nThe narrative writes itself: self-custody is broken, hardware wallets cannot be trusted, move your bitcoin to an exchange or an ETF. The opposing case requires examining what the Coldcard hack actually proved and what it did not.\nFirst, this was not a failure of self-custody. It was a failure of one company’s firmware engineering. The bitcoin protocol worked exactly as designed. The cryptography worked exactly as designed. The vulnerability existed in Coinkite’s build configuration, not in the security model of hardware wallets as a category. Ledger, Trezor, and Block have confirmed their devices are unaffected. The lesson is that seed generation must be verified independently, not that seed generation is inherently unreliable.\nSecond, the exchange alternative carries its own catastrophic risks. FTX lost $8 billion in customer funds. Mt. Gox lost 850,000 BTC. Celsius, Voyager, and BlockFi collectively lost billions more. The Coldcard exploit drained $116 million across 5,200 addresses over five days. FTX drained $8 billion from millions of users in a single night. The scale comparison favors self-custody even in its worst failure mode.\nThird, multisignature configurations would have prevented every theft in this exploit. A multisig wallet requires multiple independent keys to authorize a transaction. If even one key was generated on a non-Coldcard device, the attacker could not have completed the sweep. Casa, Unchained, and other multisig providers have reported zero customer losses from the Coldcard exploit because their architectures distribute key generation across independently designed devices from different manufacturers. A 2-of-3 multisig wallet using one Coldcard, one Ledger, and one Trezor would have been immune to this attack even if the Coldcard key was fully compromised, because the attacker would still need to independently compromise one of the other two keys. The Coldcard hack is an argument for multisig, not an argument against self-custody.\nFourth, the bitcoin price reaction undermines the catastrophic framing. Bitcoin traded near $64,300 through all four attack waves and has not broken below $63,800 since the exploit became public. The market is pricing the Coldcard hack as a company-specific event, not a systemic threat to bitcoin’s security model. If the market believed self-custody was fundamentally broken, the price response would have been severe. It was not.\nWhat would invalidate the self-custody thesis: if multiple hardware wallet manufacturers were found to have the same class of entropy flaw simultaneously, suggesting a systemic rather than idiosyncratic failure. If the attack surface expands to include devices with hardware random number generators that pass all existing tests but contain subtle biases. Or if the operational burden of key management proves permanently beyond the capacity of individual users, making professional custody the only viable option for most bitcoin holders regardless of the theoretical security advantages of self-custody.\n\n\n\n\n\n                Read more:\n            \n\n                Coldcard pushes bitcoin back to exchanges: the anti-self-custody trade            \n\nWhat to watch\n\nJUST IN: Coldcard wallets affected by security issue with reported lossesRoughly 594 $BTC valued at $38 million has been stolen from certain dormant single sig wallets pic.twitter.com/f3fk7kYXzM— crypto.news (@cryptodotnews) August 1, 2026\n\n\nGalaxy Research’s final loss tally after Wave four confirmation. The gap between 1,596 BTC (confirmed) and 2,055 BTC (estimated) represents roughly $30 million in unverified losses. If the fourth wave is confirmed and additional waves follow, the total could exceed $150 million and push the incident past Bybit’s 2025 blind-signing exploit in impact.\nOn-chain movement of attacker-controlled bitcoin. Roughly 90% of stolen funds remain unmoved. When the attacker begins laundering, the chosen method (mixing, cross-chain bridges, OTC desks) will indicate sophistication level and potentially enable attribution. TRM Labs is monitoring in real time.\nExchange inflow trends over the next 30 days. The post-Coldcard flow reversal could be a temporary panic response or the beginning of a structural shift. If net flows back to exchanges persist beyond August, it suggests a durable change in how bitcoin holders weigh self-custody risk against counterparty risk.\nIndependent audit adoption by hardware wallet manufacturers. Kraken CSO Nick Percoco called for independent testing of seed generation in production firmware. If Ledger, Trezor, and other manufacturers adopt third-party entropy audits as standard practice, it validates the systemic concern. If they do not, the industry is betting the same class of bug will not appear elsewhere.\nRegulatory response to the self-custody failure. The SEC and CFTC have not commented on the Coldcard exploit. If regulators use the incident to argue that self-custody is unsuitable for retail investors, it could accelerate the push toward mandatory custodial frameworks for digital assets.\n\nFrequently asked questions\n\n\n\nWhat is the Coldcard hardware wallet hack?\n\nThe Coldcard hack refers to a series of bitcoin thefts beginning July 30, 2026, in which an attacker exploited a firmware flaw in Coinkite’s Coldcard hardware wallet to brute-force weakly generated seed phrases and drain funds from more than 5,200 addresses without physical access to any device.\n\n\n\nHow much bitcoin was stolen in the Coldcard exploit?\n\nGalaxy Research has confirmed 1,596 BTC stolen across three attack waves, with a suspected fourth wave that could bring the total to approximately 2,055 BTC, worth close to $130 million. TRM Labs estimated confirmed losses at 1,816 BTC, approximately $116 million.\n\n\n\nWhat caused the Coldcard vulnerability?\n\nA build configuration error in firmware version 4.0.1, shipped March 2021, set a macro called MICROPY_HW_ENABLE_RNG to zero. A supporting library checked whether the macro existed rather than whether it was enabled, causing seed generation to fall back on a weak software random number generator instead of the device’s hardware entropy source.\n\n\n\nDoes updating Coldcard firmware fix the problem?\n\nNo. Updating firmware prevents new wallets from being generated with weak randomness, but it does not repair a seed that was already generated on vulnerable firmware. Affected users must generate a new seed on patched firmware, verify the new wallet, and manually migrate their funds.\n\n\n\nWhich Coldcard models are affected?\n\nAll current models are affected to varying degrees. Mk3 devices on firmware 4.0.1 through 4.1.9 had entropy reduced to approximately 40 bits. Mk4 and Mk5 devices on firmware below 5.6.0 and Q devices on firmware below 1.5.0Q had entropy reduced to approximately 72 bits. Wallets created using the dice-roll option are considered safe.\n\n\n\nAre other hardware wallets affected?\n\nNo. Block, Trezor, and Ledger have confirmed their devices use independent random number generation implementations and are not affected by the Coldcard-specific firmware flaw. The vulnerability is specific to Coinkite’s build configuration, not to hardware wallets as a category.\n\n\n\nIs self-custody still safe after the Coldcard hack?\n\nThe Coldcard hack exposed a failure in one manufacturer’s implementation, not a flaw in the self-custody security model. Multisignature wallets, which require multiple independent keys from different devices, would have prevented every theft in this exploit. Security experts recommend using multisig configurations and verifying that hardware wallet manufacturers undergo independent entropy audits.\n\n\n\nShould I move my bitcoin to an exchange after the Coldcard hack?\n\nExchange custody eliminates seed-management risk but introduces counterparty risk. FTX, Mt. Gox, Celsius, and other exchange failures collectively lost billions more than the Coldcard exploit. The decision depends on individual risk tolerance, technical capability, and the value of holdings. Bitcoin ETFs offer regulated price exposure without direct key management for investors who prioritize convenience over sovereignty. This is educational analysis, not investment advice.\n\n\n\n\nDisclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Hardware wallet security incidents carry significant risk of permanent fund loss. Past security performance of any device does not guarantee future security. Published August 5, 2026.","kind":"highlight","is_publish_news":true,"is_publish_highlight":false,"is_publish_live":false,"is_publish_wemedia":false,"editions":null,"column":"","sentiment":"0","news_tag":"","news_rank":0,"isVideo":false,"video":null,"symbols":[],"gpt_button":0,"need_auth":false,"need_login_tip":false,"code":"91000000","status":"200"},"commentList":[],"isCommentEnd":true,"newsSizeData":{"likeSize":0,"commentSize":0,"repostSize":0,"favoriteSize":0,"likeStatus":false,"favoriteStatus":false},"APP":{"userAgent":"Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)","isDev":false,"isTTM":true,"isLaohu8Offline":false,"tenantId":"TBGLOBAL","deviceId":"web-server-community-laohu8-v3","version":"4.47.1","shortVersion":"4.47.1","platform":"web","vendor":"web","appName":"ttm","isIOS":false,"isAndroid":false,"isTiger":false,"isTHS":false,"isWeiXin":false,"isWeiXinMini":false,"isWeiBo":false,"isQQ":false,"isBaiduSwan":false,"isBaiduBox":false,"isDingTalk":false,"isToutiao":false,"isOnePlus":false,"isHuaWei":false,"isXiaomi":false,"isXiaomiWebView":false,"isOppo":false,"isVivo":false,"isSamsung":false,"isMobile":false},"href":"/m/news/2657689746","isCrawlerRequest":true}