Blockchain
THORChain Refused to Block the $387M Bitget Hacker. Here’s Why | Chad Barraford
Publication: The Defiant
Author: Camila Russo
Source published: 03/11/2026, 18:07:04 UTC
Briefing created: 03/11/2026, 18:24:41 UTC
Based on a feed excerpt; full article content has not been acquired. Source evidence retrieved 03/11/2026, 18:12:24 UTC.
Briefings
THORChain refused to block Bitget's $387M hack, while Tether froze and unfroze four THORChain vaults holding 1.45 million USDT. The article notes THORChain also lost $10.7 million to a GG20 flaw in May. The evidence is limited to these specific incidents and does not provide broader context on why the refusal occurred or the full scope of the GG20 vulnerability.
Key points
- THORChain explicitly refused to block Bitget's addresses following a $387.5 million hack.
- Tether froze and subsequently unfroze four THORChain vaults on Tron containing 1.45 million USDT.
Context
The provided evidence details two specific security incidents involving THORChain: a major hack by Bitget and a smaller vulnerability loss to GG20. It does not supply background on the broader ecosystem impact of these events or the reasons for THORChain's refusal to block the Bitget addresses.
Limitations
The evidence covers only two specific incidents: a $387.5M hack and a $10.7M vulnerability loss. It lacks context on the broader consequences of the hack, the reasons for the refusal, or the full scope of the GG20 flaw.
Generated by Bittrees-hosted qwen35-2b sha256:aaf42c8b7c3c on 03/11/2026, 18:24:41 UTC. Based on publisher-provided feed evidence; may not cover the full original article. Check the source for details.
View archived briefing on IPFS
bafybeid4komz5tt67njsrixr7rcfbdjcrcpzyb4szvw3jlox2hczysjqma