THORChain Bifrost exploit vault ops is the primary keyword for this Radar update. Reports from Cointelegraph and TRM Labs describe a May 15 THORChain exploit and network halt.
Radar is covering the event as protocol operations. The focus is vault behavior, signing pauses, node assumptions and remediation transparency rather than a RUNE trading setup.
What Happened
Cointelegraph reported that THORChain paused trading after ZachXBT flagged a suspected exploit above $10 million across Bitcoin, Ethereum, BNB Chain and Base. TRM Labs reported more than $11 million drained across at least nine chains.
Both sources point to a live cross-chain security incident where trading and signing status, attacker-address tracking and remediation updates matter for users evaluating protocol reliability.
Why It Matters
For protocol researchers, the incident matters because native cross-chain swap systems depend on vault custody, node behavior and signing assumptions. A halt is not just market news; it is an operations test.
The Radar angle differs from CryptoSigy. CryptoSigy covers liquidity and trader-route risk, while Radar tracks protocol controls, vault recovery, node-operator accountability and whether future use can be justified after remediation.
What To Watch Next
Watch official THORChain status, post-mortem detail, vault recovery steps and whether independent security researchers confirm the failure path. A resume notice without root-cause clarity is not enough.
Also watch whether future design changes affect validator churn, signing thresholds or emergency pause authority. Those details decide whether protocol trust improves or simply resets.
Decision Check
For Radar, the control point is Protocol-ops angle on THORChain vault security, signing pauses, node behavior and remediation transparency.. The update should be tracked as protocol discovery only if the source path remains visible, operators or governance actors provide follow-through, and users can verify the operational change instead of relying on a headline.
The watch condition is also clear: if the protocol source does not move into implementation, post-mortem detail, governance action or verifiable operator behavior, the item should stay on the watchlist rather than become a stronger discovery signal.
Continue this cluster
Continue this cluster with May 16 protocol, chain and ecosystem updates that show how live infrastructure is changing.
