The volunteer initiative Bitcoin Red Team has presented the results of the first phase of a large-scale security audit of the first cryptocurrency's ecosystem. In the first 29.8 hours of work, researchers recorded 4,962 potential issues across 390 bitcoin-related projects. Of these, 85 findings were classified as critical risk, and 635 as high risk.

What exactly the team is checking

Bitcoin Red Team focuses on analyzing cryptographic libraries, wallets, infrastructure software, and other open-source solutions. The team consists of 16 specialists working around the clock, including Cashu protocol developer under the pseudonym Calle and AnchorWatch CEO Rob Hamilton. The methodology combines AI models with manual verification: testing tools load code, identify potentially dangerous sections, and reproduce possible attacks in a local environment.

This is classic red teaming — simulating an attacker's actions. Researchers not only look for errors but also assess whether they can be used for actual product compromise. According to Calle, participants on average find about one critical exploit per hour per person, although he does not disclose the exact counting methodology.

Reason for the audit: attacks on Coldcard

The campaign started against the backdrop of exploitation of a vulnerability in Coldcard hardware wallets. According to my data, the error appeared after firmware changes in 2021: instead of the devices' hardware random number generator, in some cases they relied on a predictable MicroPython software generator. The effective entropy of seed phrases dropped from 128 bits to approximately 40 bits for the Mk2 and Mk3 models, and to 72 bits for the Mk4, Mk5, and Q. Manufacturer Coinkite released fixes, but they do not protect already created seed phrases — owners had to generate new ones and transfer funds.

Losses from three confirmed waves of attacks exceeded $100 million, and considering a suspected fourth wave, they could reach $130 million. At least 15 different attackers exploited this error.

AI accelerates discovery, but not coordination

Hamilton noted that the campaign's main limitation is not vulnerability discovery, but delivering reports to the right developers. The team has already made more than a dozen disclosures, scanning 150 repositories, but coordination remains the most challenging part. Critical reports are first reproduced using a working attack example, then privately shared with developers. The list of affected projects has not yet been disclosed.

My comment: This initiative is an important signal for the entire industry. The scale of findings (85 critical ones per day) shows that even in mature ecosystems, open-source security often lags. However, the key challenge is not detection but timely remediation: without effective coordination between researchers and developers, even the most serious findings risk remaining unresolved, creating a window for real attacks.