Executive Overview

Canadian Bitcoin hardware manufacturer Coinkite has issued an urgent security advisory, strongly recommending that users of its Coldcard Mk3 signing device immediately migrate their funds. The warning applies specifically to wallets whose seed phrases were generated on affected firmware versions deployed between March 2021 and the end of the device’s lifecycle.

This advisory follows mounting scrutiny from Bitcoin security specialists who are actively investigating an unexplained, highly coordinated sweep of 594.48 Bitcoin (BTC)—valued at approximately $38.3 million at prevailing market rates—from single-signature addresses. While Coinkite emphasizes that no definitive public evidence has yet linked the Coldcard Mk3 firmware vulnerability directly to this massive drain, the convergence of these events has triggered industry-wide concern.

Security experts suspect that a critical flaw in randomness generation, commonly referred to as low entropy, may have compromised wallet creation. As researchers race to reverse-engineer the mechanics behind the sweeping activity, affected users are being advised to take immediate, precautionary steps to secure their holdings. This comprehensive report examines the timeline of the alert, technical analyses from leading cryptographic experts, potential attack vectors, and the broader implications for the Bitcoin hardware wallet ecosystem.

Detailed Chronology of Events

The unfolding security situation developed rapidly over a short window, moving from isolated user reports on social media to formal industry-wide warnings and coordinated investigative efforts by top-tier Bitcoin security firms.

The Initial Discovery and User Reports

The alarm bells began ringing when a user on Reddit published a detailed timeline explaining that their wallet had been completely drained. According to the user, the compromised wallet’s seed phrase had originally been generated on a Coldcard Mk3 device purchased in May 2021.

Crucially, the user noted that the seed phrase was later restored onto a newer Coldcard Mk4 hardware wallet in January 2026. This detail indicates that the seed had been entered into a second device years after its creation. While this report was self-reported and did not immediately establish a definitive causal link between Coinkite’s hardware and the wider sweep, it served as the catalyst for independent security researchers to dig deeper into historical wallet creation vulnerabilities.

The Massive 594 BTC Sweep

Shortly after the Reddit disclosure, on-chain analytics and statements from prominent security figures revealed a much larger, coordinated attack. Rob Hamilton, CEO and co-founder of digital asset custody firm AnchorWatch, published a preliminary analysis detailing a staggering blockchain event.

According to Hamilton’s findings, an attacker—or a sophisticated automated system—managed to sweep 1,324 unspent transaction outputs (UTXOs) across 500 distinct transactions packed tightly within a three-block window. In total, 594.48 BTC was extracted from unsuspecting wallets. Further analysis revealed that approximately 562 BTC of the total stolen funds was subsequently consolidated into a single destination address, pointing to a highly organized operation.

Coinkite’s Formal Warning

Prompted by the escalating discussions and early telemetry, Coinkite moved quickly to address potential vulnerabilities within its legacy hardware ecosystem. On Thursday, the company published an official advisory warning users of the Coldcard Mk3 signing device to transfer their funds away from wallets whose seed phrases were generated on affected firmware.

According to Coinkite’s early analysis, the issue impacts Mk3 units running firmware version 4.0.1—which was released in March 2021—as well as any subsequent Mk3 firmware version up to version 5.0.3, the final software update supporting the Mk3 model. Importantly, Coinkite’s preliminary investigations indicate that newer hardware generations, including the Coldcard Mk4, Q, and Mk5 models, are entirely unaffected by this specific vulnerability.

Supporting Context & Metrics: Analyzing the $38.3 Million Drain

To fully grasp the magnitude of the incident, it is essential to look at the financial and structural metrics surrounding the swept funds.

At the time of the initial disclosures, Bitcoin was trading at approximately $64,364.07, according to data from CoinGecko. Based on this price point, the total volume of swept funds—594.48 BTC—carried a fiat valuation of roughly $38.3 million.

Key Transaction Metrics:

  • Total Volume Swept: 594.48 BTC
  • Unspent Transaction Outputs (UTXOs) Involved: 1,324
  • Total Transactions: 500 distinct transactions executed within a tight three-block window
  • Consolidation: Roughly 562 BTC consolidated into a primary destination address
  • Address Types: Primarily single-signature addresses, with a heavy concentration in native SegWit formats

Security analysts immediately focused on the specific characteristics of the transactions. Rob Hamilton noted that the structural nature of the sweep strongly suggested an issue with wallet entropy. "At a glance, this looks like there was flawed entropy in wallet generation somewhere along the way," Hamilton stated in his public breakdown.

Low entropy implies that the random-number generator (RNG) used during the seed phrase creation process failed to produce a truly random sequence of words. Instead, it may have drawn from a constrained or predictable set of possibilities, drastically reducing the computational effort required for an attacker to recreate the private keys via brute-force attacks.

Technical Hypotheses and Expert Analysis

As the crypto security community collaborates to dissect the incident, several prominent industry leaders have put forward working hypotheses regarding how the alleged compromise could have occurred.

Kevin Loaec and the Low-Entropy RNG Hypothesis

Kevin Loaec, CEO of Wizardsardine, weighed in with a detailed technical hypothesis. Loaec suggested that a low-entropy random-number generator—potentially residing within a software library, a specific hardware secure element, a particular manufacturing batch, or a specific firmware version—may have failed to generate sufficient cryptographic randomness during seed creation.

Expanding on this theory, Loaec posited that an attacker who discovered or deduced the flaw could have deployed an AI-generated or highly optimized script to brute-force the affected wallets. Interestingly, Loaec pointed out a specific anomaly: the attacker appeared to search only a limited range of BIP-84 derivation paths.

This narrow scanning window could explain why the sweep appeared heavily concentrated in native SegWit addresses and why some discovered wallets were only partially drained. However, Loaec cautioned that this theory remains unconfirmed and issued a chilling warning: if his hypothesis holds true, wallets that suffered only partial drainage remain at grave risk of subsequent theft. Furthermore, he noted that funds held in other address types (such as legacy or Taproot addresses) could become vulnerable if the attacker expands their scanning parameters to include them.

Official Statements and Migration Guidance

Coinkite has maintained a transparent posture throughout the unfolding situation, emphasizing caution while its engineering and security teams conduct a thorough forensic review.

The Official Coinkite Advisory

In its official blog post, Coinkite outlined the scope of the potential risk and provided clear instructions for users who believe their setups may be compromised:

"Out of an abundance of caution, we urge affected users to generate a new seed on an unaffected device, verify its backup and receive address, send a small test transaction, and only then move the remaining funds."

The company stressed that its investigation is ongoing and promised a formal, comprehensive technical review once all forensic data has been processed.

The BIP-39 Passphrase Mitigation Factor

In a reassuring note for a subset of its user base, Coinkite indicated that early analysis suggests affected seed phrases used in conjunction with a BIP-39 passphrase face minimal risk.

The company explicitly clarified that this refers to a true BIP-39 passphrase (often referred to as a "25th word"), rather than the standard numerical PIN used to unlock the Coldcard device itself. The addition of a strong, unique BIP-39 passphrase effectively alters the seed derivation math, rendering standard brute-force attempts on the base seed phrase ineffective even if the underlying entropy was compromised.

Future Outlook: Implications for Bitcoin Hardware Security

The emergence of the Coldcard Mk3 firmware warning and its loose association with a multi-million-dollar wallet sweep serves as a critical watershed moment for the Bitcoin hardware security landscape.

1. Re-Evaluating Supply Chain and Firmware Audits

Hardware wallets have long been trusted as the ultimate fortress for cryptocurrency savings because they keep private keys isolated from internet-connected devices. However, this incident highlights the reality that firmware updates, random-number generation dependencies, and legacy device support require perpetual, rigorous auditing. As hardware wallet manufacturers iterate rapidly to add features, ensuring backward compatibility without introducing unforeseen attack surfaces remains a paramount challenge.

2. The Growing Threat of Automated Brute-Forcing

If theories regarding low-entropy generation and targeted script-based scanning prove correct, it demonstrates an alarming evolution in how attackers exploit legacy cryptocurrency setups. The use of automated scripts to scan specific derivation paths across blockchain history points to an increasingly sophisticated threat landscape where historical vulnerabilities in discontinued hardware can be systematically exploited at scale.

3. Best Practices for Self-Custody Users

For everyday Bitcoin holders, this incident reinforces several fundamental self-custody rules:

  • Keep Firmware Updated (With Caution): While upgrading firmware is generally recommended for security patches, users should monitor manufacturer communications for stability and security advisories before applying updates to legacy devices.
  • Utilize Additional Protections: Implementing a robust BIP-39 passphrase adds an essential layer of cryptographic defense, shielding wallets from certain types of seed-generation flaws.
  • Test Before You Transfer: When migrating funds from a potentially compromised device, always follow Coinkite’s advice: generate a fresh seed on a verified, unaffected device, test the backup, execute a small test transaction, and confirm receipt before moving the bulk of your capital.

As Coinkite continues its formal technical review and independent security researchers publish further on-chain forensics, the Bitcoin community will be watching closely. This event serves as a stern reminder that eternal vigilance, defense-in-depth strategies, and prompt adherence to security advisories remain the bedrock of safe cryptocurrency self-custody.