DeFi Intel

BTCPay Server Offers a 3 Bitcoin Bounty for Recovery of Stolen

Bitcoin Magazine BTCPay Server Offers a 3 Bitcoin Bounty for Recovery of Stolen Funds After Wallet Exploit The open-source payment processor is funding a recovery bounty worth 10% of any funds returned, capped at 3 Bitcoins, and says it will prioritize security patches over new features indefinitely. This post BTCPay Server Offers a 3 Bitcoin Bounty for Recovery of Stolen Funds After Wallet Exploit first appeared on Bitcoin Magazine and is written by Mathew Di Salvo .

TL;DR

BTCPay Server announced a bounty to help recover Bitcoin stolen in the Coldcard exploit, which has locked over $100 million across thousands of addresses. At the same time, BTCPay released version 2.4.5, adding SSRF protection and tighter refund rules, reflecting a coordinated push to improve security and incentivise fund recovery.

Key facts

  • The Coldcard exploit has stolen more than 1,596 BTC worth over $100 million.
  • Ninety percent of the stolen Bitcoin remains untouched in its receiving addresses.
  • BTCPay Server released version 2.4.5 with SSRF protections for Lightning and LNURL requests.
  • The update makes Tor support optional, requiring manual re‑enablement after upgrade.
  • BTCPay Server announced a bounty to encourage recovery of the stolen Bitcoin.

BTCPay Server announced a bounty to encourage the recovery of Bitcoin stolen in the Coldcard hardware‑wallet exploit, while simultaneously releasing version 2.4.5 that tightens security and improves invoice speed. The exploit, first reported in early August 2026, has affected more than 1,596 BTC valued at over $100 million across roughly 7,300 addresses. The bounty and the software update were both publicized on 10 August 2026, highlighting a coordinated response from the open‑source payment platform to a high‑profile theft that has shaken confidence in self‑custody solutions.

Background

The Coldcard exploit emerged as one of the most serious hardware‑wallet incidents in Bitcoin’s history, prompting a forensic investigation that has expanded from an initial 1,367 BTC loss to more than 1,596 BTC, with some analysts estimating total exposure near 2,000 BTC, or roughly $130 million. The theft unfolded in three confirmed waves, each moving funds to distinct addresses that have largely remained untouched, suggesting the attacker is consolidating rather than liquidating. This pattern has allowed investigators to map attacker‑controlled wallets and share verified addresses with law‑enforcement and compliance firms. The incident has reignited debate over the resilience of self‑custody, leading manufacturers like Coinkite to release emergency firmware, pause shipments, and urge users to generate fresh seeds. In parallel, BTCPay Server, an open‑source Bitcoin payment processor, issued version 2.4.5, focusing on mitigating Server‑Side Request Forgery (SSRF) vulnerabilities, tightening refund permissions, and making Tor support optional. The release follows earlier security‑focused updates in September and August 2026, reflecting a broader industry push to harden infrastructure after high‑profile breaches.

What happened

On 10 August 2026, BTCPay Server publicised a bounty aimed at recovering Bitcoin stolen in the Coldcard exploit, as reported by Ambcrypto. The same day, Ambcrypto detailed that the Coldcard exploit had grown to affect more than 1,596 BTC, worth over $100 million, across roughly 7,300 addresses, with a potential fourth wave that could raise losses to about 2,055 BTC, or $130 million, according to Galaxy Research. The exploit’s three confirmed theft waves showed that ninety percent of the stolen Bitcoin remained untouched, and each wave’s coins stayed in their receiving addresses, reinforcing investigators’ confidence in mapping the attacker’s wallet network. Meanwhile, Cointelegraph reported that Romania’s national postal service installed its first Bitcoin ATM in Tulcea, signalling broader institutional acceptance of crypto, though this development is unrelated to the theft. Cryptobriefing described BTCPay Server’s version 2.4.5 release, noting that it adds SSRF protections for Lightning and LNURL outbound requests, tightens refund permissions, hides public invoice details after one month, and makes Tor support optional, requiring manual re‑enablement after the update. The release also retired several older integrations and introduced a new command, btcpay‑routes, for better Lightning API control. Together, these actions illustrate a coordinated effort by BTCPay Server to improve security while incentivising the recovery of the stolen funds.

Market impact

The Coldcard exploit has locked up more than $100 million in Bitcoin, with ninety percent of the stolen coins remaining unspent, limiting immediate market supply pressure. The potential fourth wave could add roughly $30 million in locked value, pushing total exposure toward $130 million. BTCPay Server’s bounty may stimulate recovery attempts that could eventually release some of the dormant coins, modestly affecting circulating supply. The release of version 2.4.5, by tightening SSRF defenses and refund controls, may reduce the risk of further thefts from merchants using the platform, potentially preserving transaction volumes on BTCPay‑powered stores. Romania’s new Bitcoin ATM expands retail access but, given the low global Bitcoin ownership rates—about 4 percent of the world population and 14 percent in the United States—its immediate market impact remains limited.

Why it matters

The scale of the Coldcard exploit challenges the long‑standing belief that self‑custody is inherently secure, highlighting the importance of robust wallet design, independent entropy generation, and multisig safeguards. The fact that most stolen coins remain untouched suggests that attackers are prioritising consolidation, which gives investigators a window to trace and potentially recover funds, especially with incentives like BTCPay Server’s bounty. BTCPay Server’s security upgrades address a critical attack vector—SSRF—that could otherwise allow malicious actors to reach internal services, thereby protecting merchants and their customers. By making Tor support optional, the update also forces operators to consciously manage privacy configurations, reducing inadvertent exposure. Together, these developments underscore a broader industry shift toward proactive security measures and collaborative recovery efforts in the wake of high‑value thefts.

DeFi Intel’s take

Editorial analysis, not a statement of fact.

DeFi Intel's take: the combination of a targeted bounty and a hardening of BTCPay Server’s codebase suggests the community is moving from reactive patching to proactive incentive‑driven recovery. We read this as an acknowledgment that technical fixes alone cannot undo large‑scale thefts, and that financial incentives may help tip the balance toward reclaiming dormant coins. The emphasis on SSRF mitigation and stricter refund permissions indicates that platform operators are learning from recent exploits and tightening internal controls. While the bounty’s exact size is not disclosed, its existence signals that open‑source projects are willing to allocate scarce resources to address systemic risks, a trend that could encourage similar actions across the ecosystem.

Sources used for this analysis

DeFi Intel wrote this analysis from the reporting above. Any figure or quotation can be checked against those pages.

Frequently asked questions

What is the scale of the Coldcard exploit?

The exploit has affected more than 1,596 Bitcoin, valued at over $100 million, across roughly 7,300 addresses. Some analysts see a possible fourth wave that could raise total losses to about 2,055 Bitcoin, or $130 million.

What security changes does BTCPay Server 2.4.5 introduce?

Version 2.4.5 adds protections against Server‑Side Request Forgery for Lightning and LNURL requests, tightens refund approval permissions, hides public invoice details after one month, and makes Tor support optional, requiring manual re‑enablement.

How does the bounty relate to the stolen Bitcoin?

BTCPay Server announced a bounty to encourage the recovery of the Bitcoin stolen in the Coldcard exploit, aiming to incentivise efforts that could return some of the locked funds to legitimate owners.

Read full article on Bitcoinmagazine →

DeFi Intel is an entity-graph aggregator: we curate, tag and link crypto news to a typed knowledge graph of protocols, tokens, people and incidents. We do not republish the full article body. Use the link above to read the original report at Bitcoinmagazine.

Discussion

Comments are reviewed before publication.

No comments yet.

Stay current on entity-tagged crypto news

Get the weekly DeFi Intel brief — entity-graph intelligence covering protocols, tokens and incidents, free to your inbox.