Galaxy

2026

Read

would

Bitcoin

<p>Galaxy Research raised its estimate of Bitcoin drained from addresses linked to the Coldcard firmware flaw to 1,367.05 BTC, worth about $88.6 million, on Aug. 1.&nbsp;</p>
<div id="cn-block-summary-block_14d071495e76f5d02fa12d3fb018aea4" class="cn-block-summary">
 <div class="cn-block-summary__nav tabs"><span>Summary</span>
 </div>
 <div class="cn-block-summary__content">
  <ul>
   <li>1,367.05 BTC was drained across 4,585 addresses in three suspected Coldcard attack waves, Galaxy reported.</li>
   <li>July 30’s first wave removed 1,082.65 BTC from 1,196 addresses in just 41 minutes total.</li>
   <li>Firmware updates fix new seed generation but cannot repair vulnerable seeds created on earlier releases.</li>
  </ul>
 </div>
</div>
<p>The research unit identified 4,585 affected addresses across three suspected attack waves, replacing its earlier estimate of 1,082.65 BTC from 1,196 addresses.</p>
<p>The revised figure means the $70.2 million estimate reported after Galaxy’s first <a href="https://x.com/glxyresearch/status/2083181683067506899" rel="noopener noreferrer nofollow">analysis</a> is no longer current. Galaxy described the total as its “estimated observed size,” leaving open the possibility that further transactions could be found. The company has not proved that every address came from a vulnerable Coldcard seed.</p>
<figure class="wp-block-embed is-type-rich is-provider-x wp-block-embed-x">
 <div class="wp-block-embed__wrapper">
  <blockquote class="twitter-tweet">
   <p>We mapped the flow of funds for the Coldcard vulnerability based on the pattern identified by engineers at Block and shared by <a href="https://x.com/clay_garrett?ref_src=twsrc%5Etfw" rel="noopener noreferrer nofollow">@clay_garrett</a><br><br>1,196 addresses drained in full for 1,082.65 BTC (~$70.2M) between 01:10:20 and 01:51:26 UTC on Jul 30 — a 41-minute window, blocks… <a href="https://t.co/q785paZvMQ" rel="noopener noreferrer nofollow">pic.twitter.com/q785paZvMQ</a></p>— Galaxy Research (@glxyresearch) <a href="https://x.com/glxyresearch/status/2083181683067506899?ref_src=twsrc%5Etfw" rel="noopener noreferrer nofollow">July 31, 2026</a>
  </blockquote>
 </div>
</figure>
<h2 class="wp-block-heading" id="strong-galaxy-raises-coldcard-estimate-after-third-wave-strong"><strong>Galaxy raises Coldcard estimate after third wave</strong></h2>
<p>Galaxy’s first mapped wave occurred between 1:10:20 a.m. and 1:51:26 a.m. UTC on July 30. It traced 1,082.65 BTC from 1,196 addresses across blocks 960,183 through 960,191. The transactions appeared about 30 hours before Coinkite issued its initial public advisory.</p>
<p>A second wave on July 31 drained 76.16 BTC from another 1,478 addresses. Galaxy later identified a <a href="https://x.com/glxyresearch/status/2083623500183421043" rel="noopener noreferrer nofollow">third wave</a> that removed 207.7294 BTC from 1,912 addresses. Together, the three groups brought the observed total to 1,367.05 BTC across 4,585 addresses.</p>
<p>The first wave used the same 30 satoshis per virtual byte fee and transactions without change outputs. Those traits helped researchers identify the related movements onchain. Galaxy warned that later attacks might use different patterns, making the complete loss harder to measure.</p>
<h2 class="wp-block-heading" id="strong-three-waves-used-different-transaction-patterns-strong"><strong>Three waves used different transaction patterns</strong></h2>
<p>Galaxy said the first two waves shared collector addresses, destination types and derivation-path behavior. The events also occurred about 27 hours apart. Those similarities suggested one operator may have conducted both sweeps, although the blockchain cannot establish the attacker’s identity.</p>
<p>The third wave behaved differently. Funds from each victim moved to separate pay-to-witness-script-hash destinations, while several victims were grouped into each sweep transaction. The activity also checked only the default derivation path. Galaxy said it was confident each wave represented one operator, but would not claim that one attacker controlled all three.</p>
<p>Therefore, descriptions of a single hacker remain an inference rather than a confirmed fact. Galaxy called the third group “what we suspect are hacks of Coldcard-generated addresses.” The wording reflects the limits of onchain attribution.</p>
<p>Coinkite said a series of firmware integration errors prevented the intended hardware random-number generator from contributing properly to seed creation. A MicroPython software fallback supplied predictable output after a March 2021 code change. <a href="https://engineering.block.xyz/blog/predictable-rng-fallback-and-32-bit-reseed-in-coldcard-firmware" rel="noopener noreferrer nofollow">Block’s independent technical report</a> described the same random-number-generator path and said active exploitation was underway.</p>
<p>Coinkite estimated about 40 bits of effective search space for affected Mk2 and Mk3 seeds. Later Mk4, Q and Mk5 models included extra secure-element entropy, but the company estimated roughly 72 bits rather than the intended 128 bits. These figures remain technical estimates and may change as testing continues.</p>
<p>The affected Mk2 and Mk3 range covers firmware 4.0.1 through 4.1.9. Seeds created on Mk4 and Mk5 before standard version 5.6.0, and Q seeds created before version 1.5.0Q, are also affected. Separate fixed Edge releases are available.</p>
<h2 class="wp-block-heading" id="strong-existing-seeds-require-migration-not-only-updates-strong"><strong>Existing seeds require migration, not only updates</strong></h2>
<p>Coinkite released hotfixes for every affected model and said it takes “full accountability” for the bug. However, installing new firmware only corrects future seed generation. It cannot add entropy to a recovery phrase that already exists.</p>
<p>The <a href="https://blog.coinkite.com/coldcard-mk3-seed-generation-warning/" rel="noopener noreferrer nofollow">official Coldcard advisory</a> tells users to install the fixed firmware, generate a completely new seed, verify its backup and receiving address, and send a small test transaction before moving the remaining balance. Users should keep the previous backup until the migration is confirmed.</p>
<p>Coinkite said seeds created with at least 50 fair, independent and private dice rolls are not considered exposed by this issue alone. A strong, unique BIP-39 passphrase adds another barrier, but the company still advises migration. Short, reused or predictable passphrases may not provide adequate protection.</p>
<p>However, <a href="https://crypto.news/coldcard-mk3-warning-follows-38m-bitcoin-drain/" rel="noopener noreferrer nofollow">the 594.48 BTC sweep identified</a> by AnchorWatch’s Rob Hamilton. <a href="https://crypto.news/coldcard-firmware-bug-drains-38-million-bitcoin/" rel="noopener noreferrer nofollow">In related coverage</a>, a later technical review examined how the firmware build error weakened Coldcard seeds for more than five years.</p>
<p>Coinkite’s investigation remains open, and the company has promised a formal technical review. Galaxy may also revise the observed loss again if new address patterns emerge. Until those reviews are complete, $88.6 million is the latest public estimate, not a final confirmed total. No verified Bitcoin price reaction has been attributed to the Coldcard incident so far.</p>
<p>Read more: <a href="https://crypto.news/russia-bans-moscow-crypto-mining-from-aug-15/" rel="noopener noreferrer nofollow"> Russia bans Moscow crypto mining from Aug. 15 </a></p>

Coldcard Bitcoin losses rise to $88.6M in third wave

Table of Contents

crypto.news

Other articles published on Aug 2, 2026

Join our free newsletter for daily crypto updates!