Bounty

DeFi

THORChain

Security

<p>V12 Security has ignited a sharp controversy in the DeFi space by accusing THORChain of silently fixing a major loss of funds vulnerability that the firm had responsibly disclosed in late April, while offering neither credit nor any bounty reward.</p>
<p>The accusation, detailed in <a href="https://x.com/v12sec/status/2061401842324820205?s=20" rel="noopener noreferrer nofollow">posts on X</a> and supported by shared chat screenshots and a public proof of concept repository, highlights ongoing challenges around bug bounty programs in decentralized protocols, especially amid rising AI generated spam submissions.<br></p>
<blockquote class="twitter-tweet">
 <p>We reported a critical loss of funds bug to <a href="https://x.com/THORChain?ref_src=twsrc%5Etfw" rel="noopener noreferrer nofollow">@Thorchain</a> (32M TVL, 150M FDV)</p>
 <p>They silently patched it and told us their bug bounty program is permanently retired.</p>
 <p>We have more Thorchain chain halt DoS vulns. We intend to release them (open disclosure) in the coming few days <a href="https://t.co/R2jyej5Pnh" rel="noopener noreferrer nofollow">pic.twitter.com/R2jyej5Pnh</a></p>
 <p>— V12 (@v12sec) <a href="https://x.com/v12sec/status/2061401842324820205?ref_src=twsrc%5Etfw" rel="noopener noreferrer nofollow">June 1, 2026</a></p>
</blockquote>
<h2 id="the-disclosed-vulnerability">The Disclosed Vulnerability</h2>
<p>On April 28, V12 says it reached out to the THORChain team with details of a critical flaw in the protocol’s attestation and finality mechanism. According to the researcher, a single malicious validator acting as a CometBFT block proposer could forge unsigned finality data, bypassing confirmation requirements and triggering premature outbound fund releases before source chain deposits were fully verified.</p>
<p>This issue reportedly impacted every external chain connected to THORChain and could be exploited during routine validator proposer rotations. V12 provided a detailed report, patch suggestion, and working proof of concept.</p>
<h2 id="link-to-may-exploit-and-patch-timeline">Link to May Exploit and Patch Timeline</h2>
<p>The disclosure came just weeks before <a href="https://cryip.co/thorchain-exploited-for-over-10-million-in-crypto-assets-across-multiple-chains/" rel="noopener noreferrer nofollow">THORChain suffered a real world 10.7 million</a> dollar exploit on May 15, when attackers drained funds from one of its Asgard vaults across multiple chains including Bitcoin, Ethereum, BSC, and Base.</p>
<p>THORChain developers merged a related patch titled “sign full <a href="https://gitlab.com/thorchain/thornode/-/commit/af46db22bdfe0c6ce9ec5ee9f4178442318d8eff" rel="noopener noreferrer nofollow">ObservedTx wrapper</a> to prevent proposer forgery” on May 6. However, the fix reportedly failed automated testing and was not deployed in time, contributing to the successful attack. The protocol maintains that the bug reported by V12 is unrelated to the May 15 incident.</p>
<h2 id="bug-bounty-dispute-intensifies">Bug Bounty Dispute Intensifies</h2>
<p>When V12 followed up regarding compensation, a THORChain representative allegedly informed them that the protocol’s bug bounty program had been permanently retired. THORChain has confirmed the program was closed prior to V12’s submission due to an overwhelming number of low quality, AI generated reports. The decision was publicly documented in the project’s GitLab repository.</p>
<p>This marks another chapter in THORChain’s bumpy history with security disclosures. The protocol previously ran a 500,000 dollar bug bounty on Immunefi after earlier exploits but moved away from the platform amid past controversies.</p>
<h2 id="broader-context-and-thorchain-s-security-track-record">Broader Context and THORChain’s Security Track Record</h2>
<p>THORChain, which facilitates native cross chain swaps and currently holds around 30 million dollars in TVL, has faced repeated security incidents since its early days. The <a href="https://blog.thorchain.org/thorchain-exploit-report-1" rel="noopener noreferrer nofollow">May 15 exploit</a> led to a network wide halt lasting approximately 13 hours, with no direct impact on individual user swaps. The team has since released patches and opened community governance discussions (ADR 028) on fund recovery through Protocol Owned Liquidity without minting new RUNE tokens.</p>
<p><img src="https://cryip.co/wp-content/uploads/2026/06/chart-1-750x375.jpeg" alt="" width="750" height="375"></p>
<p><a href="https://www.coingecko.com/en/coins/thorchain" rel="noopener noreferrer nofollow">RUNE token</a> reacted sharply to the May exploit, dropping as much as 15 percent in a single day and trading near 0.49 dollars recently, reflecting lingering investor concerns.</p>
<h2 id="upcoming-disclosures-and-community-reaction">Upcoming Disclosures and Community Reaction</h2>
<p>V12 has already published one proof of concept repository and warns it holds additional chain halt denial of service vulnerabilities affecting THORChain, which it plans to open source in the coming days. The firm criticized the overall code quality of the protocol.</p>
<p>The incident has divided the crypto security community. While some defend THORChain’s decision to curb low effort submissions, others including on chain investigators have pointed to persistent weaknesses in the protocol’s validator and signature systems.</p>
<h2 id="what-s-next">What’s Next?</h2>
<p>As THORChain works on recovery proposals and further hardening its infrastructure, this episode underscores the delicate balance between encouraging responsible disclosure and managing operational realities in public bug bounty programs. The DeFi space continues to grapple with sophisticated attacks and the sustainability of security incentives.</p>
<p>THORChain has not issued a full public response to V12’s latest claims beyond confirming the bounty program status.</p>

Security Researcher V12 Accuses THORChain of Silent Fix on Critical Vulnerability, Sparking Bounty Program Controversy

Table of Contents

CRYIP

Other articles published on Jun 2, 2026

Join our free newsletter for daily crypto updates!