Morning Edition · Sunday, November 22, 2026Published at 12:39 AM EST · New York
Loupe, an artificial-intelligence scanner from Block's open-source unit Spiral, found the flaw. It is the second set of machine-found node bugs that Bitcoin Core has disclosed in about a month.

Bitcoin Core, the dominant implementation of the Bitcoin node software, shipped fixes on Friday for a bug that let one connected peer stall a node. The project rated it medium severity. Loupe found it. Loupe is an open-source scanner from Spiral, Block's open-source unit, and it uses artificial-intelligence (AI) agents to examine Bitcoin code.
The attack works through transaction announcements. Nodes tell their peers about new transactions in batches of inventory messages, and the software did not skip repeated entries. An attacker could first send an orphan transaction, meaning one whose parent transactions the node has not yet seen, with thousands of missing parents. The attacker could then send inventory messages that repeat that transaction's ID 50,000 times. MLQ.ai reported that each stall could last more than ten seconds. After the fix, the node processes each transaction in a batch only once.
Elias Rohrer runs Loupe at Spiral, and Bitcoin Core developer Gregory Sanders wrote the fix. One timeline says the report was filed on July 8 and the fix was merged in August, according to KuCoin News. That leaves a gap of several months between the patch and public disclosure. The fix ships in versions 30.5 and 31.3. The 29.x series no longer receives support, so operators still running it remain exposed.
In late October, Bitcoin Core disclosed three other Loupe-found bugs. The most serious let a peer feed a node data until it ran out of memory and crashed on Windows, macOS and BSD systems, while Linux nodes were reported unaffected. Those were the first disclosures under a new Bitcoin Core policy for flaws that AI tools can easily rediscover. The policy assumes that once a scanner can find a bug, an attacker with the same tool can find it too.
The stall bug threatened neither consensus nor user funds. A stalled node relays transactions and blocks late. That matters most to miners, exchanges and Lightning operators, who need an up-to-date view of the network. Not everyone reads the case as a breakthrough. One AI-industry commentary argued that the find does not make automated scanning a replacement for human review. The record so far supports that narrower claim. Loupe finds resource-exhaustion bugs in peer-to-peer code, and humans still write and review the fixes.
Part of a tracked trend
Unaudited Open-Source Crypto Code Surfaces at Scale
Coordinated volunteer and AI-assisted review keeps exposing large backlogs of undiscovered defects in the open-source libraries that wallets, nodes and protocols depend on, so disclosure waves — not novel attacker research — become a recurring driver of emergency patches and incident risk across the ecosystem.
Start a discussion in Townsquare.
More from this edition
What this means
Cheap AI scanning lowers the cost of finding peer-to-peer bugs for defenders and attackers alike, so node operators on unsupported releases such as 29.x face rising exposure. The likelier outcome is more medium-severity Bitcoin Core disclosures within months, and a disclosed bug that splits consensus or puts funds at risk would change that assessment.
What to watch
Observations to monitor, not financial advice.
Synthesized from: CoinDesk · MLQ.ai · CryptoSlate · TFTC
Comments
0No comments yet.