Today we lost tens of millions of dollars to two separate attacks. Both are worth understanding. They're not the same problem, and they don't have the same solution.
Attack 1: COLDCARD Firmware $38M–$70M in Bitcoin
COLDCARD is one of the most respected Bitcoin hardware wallets on the market. On July 31, 2026, a firmware vulnerability disclosed by Block's security team was actively exploited 594 BTC (approximately $38M at time of disclosure, with totals reported as high as 1,082 BTC/$70M+ as more wallets were drained) disappeared in approximately 25 minutes.
The root cause: a build setting in firmware versions 4.0.0 through 5.0.3 silently disabled the hardware true random number generator. The code that was supposed to check whether the HWRNG was active only verified that the disable setting existed not whether it was actually enabled. With the hardware RNG skipped, seed generation fell back to a software PRNG seeded from the device serial number and internal clock registers both values that are observable and public.
Effective entropy dropped from 128 bits to approximately 40 bits. That makes private keys brute-forceable.
The vulnerable commit is dated March 1, 2021. The flaw went undetected for more than five years. Affected wallets: Mk2 and Mk3 with those firmware versions. If your seed was generated in that window, the seed itself is compromised updating firmware doesn't fix it. You need a new seed and to move funds.
What would have caught this? Not a Solidity audit. Not an EVM security scan. A firmware security audit specifically, NIST SP 800-90A/B/C compliance testing of the RNG implementation. This is a different discipline from smart contract auditing entirely. The code that failed is embedded C in a hardware security module, not a blockchain contract.
Attack 2: CryptoDAO (Pro Token) $8.2M on BNB Chain
On July 29–30, CryptoDAO lost $8.2M USDT from a vault contract on BNB Chain.
The root cause: a vault function with no access control. Any address could call it. The attacker combined flash loans to scale the drain.
This is one of the oldest, most well-documented vulnerability patterns in smart contract security. Missing access control functions that should be restricted to an owner or role but are publicly callable appears in almost every security audit checklist. The SWC registry lists it as SWC-105. Every major Solidity security tool flags it. It has been the root cause of hundreds of millions in losses across the history of DeFi.
What would have caught this? A smart contract audit. An automated scanner. A peer code review. Any one of these would have flagged an unprotected state-changing function on a vault holding $8M in user funds.
The Pattern of 2026
H1 2026 saw $1.1 billion stolen across 212 confirmed incidents the highest first-half figure on record, according to Blockaid's July 2026 report. The distribution is striking:
The two largest incidents (KelpDAO ~$290M, Drift Protocol ~$285M) were attributed to North Korea-linked actors and involved infrastructure compromise key theft, social engineering not smart contract bugs
CEX hacks (CoinDCX $44M, BigONE $28M, WOO X $12M) were driven by employee phishing, malware, and social engineering
DeFi protocol losses included both smart contract bugs (CryptoDAO, Lien Finance, Allbridge) and off-chain key compromise (Ostium $23.75M, AFX Trade $24.15M, B2 Network)
The Rekt News editorial published today is titled "Wrong Attack Surface." The observation: "The primary threat is no longer smart contract code but rather keys, signers, and people around the code." COLDCARD is the clearest single-day illustration of this shift.
What This Means for Developers
The security stack for a crypto project in 2026 has multiple layers, and each layer has its own failure modes:
Layer 1 Smart contract code
Covers: reentrancy, access control, integer overflow, oracle manipulation, flash loan attack surfaces, proxy storage collisions, MEV exposure, denial of service.
How to defend: smart contract audits (manual + automated), fuzzing, formal verification.
Tools: SmartContractAuditor.ai, Slither, Echidna, Certora.
Layer 2 Key management and custody
Covers: hot wallet security, hardware wallet firmware integrity, signer key compromise, multi-sig configuration.
How to defend: hardware security modules, multi-sig with geographic distribution, key ceremony protocols, firmware audits.
The COLDCARD attack lives here.
Layer 3 Off-chain infrastructure
Covers: oracle signer security, bridge validator key management, API endpoint security, server access controls.
How to defend: penetration testing, infrastructure security reviews, monitoring for anomalous signer behavior.
The Ostium ($23.75M) and AFX Trade ($24.15M) attacks from earlier this month live here.
Layer 4 Human and operational
Covers: phishing, social engineering, insider threats, third-party dependencies.
How to defend: security awareness training, separation of privileges, background checks, limited blast radius per role.
CoinDCX ($44M, employee malware) and Drift Protocol ($285M, social engineering) live here.
The Honest Position
A smart contract audit including AI-powered tools like SmartContractAuditor.ai defends Layer 1. It catches what's in the code: the access control failures, the reentrancy vectors, the oracle manipulation surfaces. The CryptoDAO hack ($8.2M) is exactly what these tools exist to prevent.
They don't catch firmware bugs in hardware wallets. They don't catch bridge validator key theft. They don't catch phishing attacks on engineering team members.
That's not a flaw in the category it's an accurate scope boundary. The mistake is treating "we got an audit" as a complete security posture when the attack surface extends well beyond the contract itself.
The COLDCARD flaw sat undetected for five years in hardware that millions of Bitcoin holders trusted. The CryptoDAO vault function sat unprotected for however long it was live, waiting for someone to call it.
Both should have been caught. Neither required a sophisticated attacker. Both were preventable by applying the right defense to the right layer.
Practical Steps for Projects Right Now
Scan your contracts free, takes 60 seconds, catches the CryptoDAO class of vulnerabilities: smartcontractauditor.ai
Check your wallet approvals if you've ever used DeFi, you have open approvals that didn't expire: smartcontractauditor.ai/wallet-approval-checker
Audit your key management who has signing authority for your treasury, bridge validators, oracle signers? Treat key compromise as an active threat model, not an edge case
Update COLDCARD firmware if you hold BTC on Mk2/Mk3, generate a new seed and migrate now. Firmware update alone is not sufficient
Written by Duron Epps, Founder of SmartContractAuditor.ai. Data sourced from CoinDesk, Bitcoin Magazine, CryptoTimes, Blockaid H1 2026 Report, Rekt News. July 31, 2026.
Top comments (0)