AIToday
AI Coding AssistantsAI Safety & AlignmentHacker NewsPublished: Aug 5, 2026, 22:01 JST3 min read

Coldcard security flaw evaded AI code review

Coldcard security flaw evaded AI code review

Key takeaway

  • Coldcard, a Bitcoin hardware wallet maker, has disclosed a firmware vulnerability that evaded detection by AI-assisted code review tools, including frontier models such as Kimi K3, Claude Fable, and Codex 5.6.

  • The bug lived at a boundary between two unrelated software submodules and persisted silently across multiple releases.

  • The company is urging users whose wallet seeds were generated with the affected firmware—without robust dice-roll entropy or a strong passphrase—to move their funds immediately, and is warning the broader Bitcoin industry that similar gaps in AI detection may exist in their own code.

3 Key Points

  1. What happened

    Coldcard, a Bitcoin hardware wallet maker, disclosed a firmware bug that went undetected by both its own AI-assisted code review and testing against frontier AI models including Kimi K3, Claude Fable, and Codex 5.6. The bug lived at a boundary between two unrelated submodules and silently persisted across multiple releases. Coldcard is urging users whose seeds were generated with the affected firmware—without at least 50 independent, private dice rolls and without a strong, unique BIP-39 passphrase—to move funds to a new wallet immediately.

  2. Why it matters

    The flaw demonstrates that current AI-assisted code review tools have blind spots in security-critical systems, particularly at build and submodule boundaries rather than in core cryptographic logic. Coldcard is publishing a historical disclosure resource (coinkite.com/historical-disclosures) and warning the broader Bitcoin hardware and software industry that similar vulnerabilities may exist in their own code, because the bug's invisibility to AI detection suggests a systemic gap in automated security tooling.

  3. What to watch

    Coldcard plans to publish a full post-mortem as its investigation continues, and it is recommending that any team relying on AI review of security-critical code test specifically against build and submodule boundaries. The company states it is supporting affected customers directly and urging others to identify and reach out to potentially impacted users.

Ask the AI about this article →

Context & Analysis

Coldcard's disclosure reveals a critical limitation in current AI-assisted code review for security-critical applications: the tools tested—including Kimi K3, Claude Fable, and Codex 5.6—all failed to catch a vulnerability that persisted across multiple firmware releases. The bug's location at a submodule boundary, rather than in core cryptographic logic, appears to have been the reason it remained invisible to both Coldcard's own AI-assisted review (conducted in the weeks before the exploit) and subsequent testing against frontier models. This suggests that AI code review tools may have systematic blind spots in detecting anomalies at integration points between separate code components, even when the flag check itself appeared superficially correct.

Coldcard's response—publishing a historical disclosure resource and recommending that other Bitcoin projects test AI tools specifically against build and submodule boundaries—indicates the company views this as an ecosystem-wide warning rather than an isolated incident. The statement that "many Bitcoin projects, including those that rely on open-source code, require immediate review" underscores the company's belief that similar vulnerabilities may be hiding in code elsewhere, undetected by the same AI tools that other teams rely on. This framing positions the flaw not as a failure of Coldcard alone, but as evidence of a gap in the current generation of AI security tooling that affects the broader Bitcoin hardware and software industry.

FAQ

Which AI models did Coldcard test against after the exploit was discovered?
Coldcard tested its code against frontier models including Kimi K3, Claude Fable, and Codex 5.6, and none of them caught the vulnerability.
Who is at risk and what should they do?
Users whose seeds were generated with the affected Coldcard firmware are at risk if their funds are not protected by at least 50 independent, private dice rolls and a strong, unique BIP-39 passphrase. Those users should move their funds to a new wallet now.
Where did the bug hide in the code?
The bug lived at a boundary between two unrelated submodules, not in the parent code or in the cryptographic and Bitcoin-specific logic that are typically the focus of internal and third-party reviews.

Get the latest AI Coding Assistants news every morning

For example, today's edition would include:

  • OpenClaw 2.0 launches, targeting enterprise AI teamsVentureBeat AI · 7h ago
  • AI Coding Shifts from Prompts to Context to HarnessITmedia AI+ · 14h ago
  • Workday brings AI agents into Gmail, keeping ERP guardrailsSiliconANGLE AI · 16h ago

AI-summarized, only the topics you pick — one digest a day via Email, Slack, or Discord.

Free · takes 30 seconds · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. Q&As are published on this page for other readers too.

Related Articles

Next articleMacPaw taps Liquid AI for on-device inference in SetApp