Quick answer (October 2026): On May 20, 2026, THORChain disclosed its third major security incident: a flaw in the signing path for outbound transfers let an attacker withdraw funds from its pooled cross-chain vaults. Users with funds in pools, savers or swaps in progress at the time were affected and should follow only official THORChain channels. GhostSwap swaps need no account, so there is no pool, savings or balance for you to leave on the platform.
THORChain, the cross-chain liquidity protocol that powers native asset swaps between Bitcoin, Ethereum, Cosmos and other chains, disclosed its third major security incident this week. The pattern is consistent with prior threshold-signature and bridge-style failures, and it matters for anyone routing swaps through pooled cross-chain infrastructure.
TL;DR: A vulnerability in THORChain's signing layer led to attacker-controlled withdrawals from cross-chain vaults. Users with funds in pools, savers, or in-flight swaps at the moment of the incident are the affected population. Non-custodial pass-through swap services like GhostSwap do not pool user funds and have a different risk surface, smaller blast radius, but not zero risk.
What happened
THORChain disclosed a security incident on 2026-05-20 affecting its cross-chain vault system. Per the protocol's status updates and on-chain analysis published by rekt.news (rekt.news/thorchain-may-2026/, retrieved 2026-05-21), the attacker exploited a flaw in the multi-party signing path used to authorise outbound transfers from THORChain's vaults to native chains.
This is THORChain's third major incident. The 2021 attacks, both the July ETH router exploit ($8M) and the subsequent August re-exploit ($8M), were post-mortemed in detail by the protocol team and external analysts (rekt.news/thorchain-rekt/, 2021-07; rekt.news/thorchain-rekt2/, 2021-08). Both root causes were partially socialised through public post-mortems and code fixes, but the underlying architectural reality, pooled cross-chain vaults secured by a threshold-signature committee, has not changed.
Bridges and bridge-adjacent protocols have been the single largest source of crypto theft by dollar value in recent years. Chainalysis' 2023 Crypto Crime Report attributes roughly $2 billion in 2022 alone to bridge exploits, making them the dominant attack class of that period (chainalysis.com/blog/2022-biggest-year-ever-for-crypto-hacking/, 2023-02). The pattern has continued through 2023 and 2024.
Why the architecture matters
THORChain uses a model where validators jointly custody assets in vaults via a threshold signature scheme (TSS). When you swap BTC for ETH on THORChain, your BTC is sent to a vault address controlled by the validator set, and ETH is paid out from another vault on Ethereum. The vaults are the honeypot.
The specific TSS construction matters. The GG20 protocol, one of the most widely deployed ECDSA threshold signature schemes, has had documented edge cases since publication. The 2021 "TSSHOCK" disclosure by Verichains identified practical attacks against several GG18/GG20 implementations (verichains.io/tsshock/, retrieved 2026-05-21), and academic follow-ups have continued to surface implementation pitfalls. The combination of TSS complexity, validator-set churn, and cross-chain bridge logic is the surface that has repeatedly failed across the bridge sector.
The trade-off is real: TSS-based bridges enable native cross-chain swaps without wrapped tokens. That is a genuine UX win. The cost is that a single class of bug in the signing path can drain a vault.
What it means for swap users
- If you had funds in THORChain pools, savers, or were mid-swap at the time of the incident, follow the protocol's official communications (twitter.com/thorchain, thorchain.org). Do not act on third-party claims of refunds or recovery tools; phishing follows every major incident.
- If you use THORChain occasionally for swaps, the same architectural risk has applied since launch. A successful exploit does not change the risk model; it confirms it. Decide whether the UX of native cross-chain swaps is worth the pooled-custody exposure for you.
- If you are looking for an alternative routing approach, services that pass funds through without pooling them have a different (not necessarily smaller in all dimensions) risk profile. More on that below.
Non-custodial pass-through vs. pooled-vault bridges
GhostSwap is a non-custodial pass-through swap service. The architecture differs from THORChain's in a specific way:
| Feature | Pooled-vault bridge (e.g., THORChain) | Non-custodial pass-through (GhostSwap) |
|---|---|---|
| Custody model | Validator set jointly custodies pooled vaults | Funds pass through; we never hold them |
| Attack surface for users not actively swapping | Yes, pooled funds at rest | None, no funds at rest |
| Routing | On-chain validator consensus | Floating-rate pricing from aggregated liquidity from leading crypto markets |
| Account / KYC | None | None, no account, no email, no identity verification |
| Pair coverage | ~10–15 chains, curated | 1,600+ pairs across 200 assets |
| Typical completion | Varies by chain | Median ~8 minutes; p95 ~30 minutes |
This is not a "GhostSwap is safer in every dimension" claim, it is not. Pass-through services rely on the liquidity layer behind them, and route quality varies. Counterparty risk shifts; it does not disappear. What changes is that there is no pool of user funds sitting in a smart contract waiting to be drained. A smaller blast radius is not the same as zero risk.
How to swap if you are migrating off THORChain
If you previously used THORChain for, say, BTC → ETH or BTC → XMR, the no-account pass-through flow looks like this:
- Pick the pair, for example, BTC to XMR or BTC to ETH.
- Paste your destination address (the wallet that will receive the swapped coin).
- Paste a refund address (so you can recover the sent coin if the swap fails or you cancel).
- You get a deposit address and a quoted rate. Floating-rate means the rate is set when your funds arrive on-chain, not when you click, typically within the quoted spread.
- Send the source coin. Median completion ~8 minutes.
No account. No email. No identity verification. The live swap widget on the homepage carries the same flow.
FAQ
Q: Was GhostSwap affected by the THORChain exploit?
A: No. GhostSwap does not route through THORChain. Funds pass through; we never hold them, and we do not have pooled vaults that could be drained by an exploit of this class.
Q: Are non-custodial swaps risk-free?
A: No. Counterparty risk shifts to the liquidity layer and route quality varies. What changes is that there is no pool of user funds at rest. A smaller blast radius is not the same as zero risk.
Q: If I had funds in THORChain at the time of the incident, what should I do?
A: Follow the official protocol channels (thorchain.org, twitter.com/thorchain) for guidance and the recovery plan, if any. Be aware that phishing attempts spike after every major incident, do not click recovery links from unsolicited DMs or new accounts.
Q: Will GhostSwap still support swaps to chains that used THORChain liquidity?
A: GhostSwap aggregates liquidity from leading crypto markets and does not depend on any single venue. Specific pairs are listed on the homepage swap widget and the per-pair pages.
Where to swap
If you are evaluating alternatives in light of this week's incident, the GhostSwap homepage swap widget carries the no-account flow. For the highest-volume pairs, see the dedicated pair pages: BTC to XMR, BTC to ETH, BTC to SOL.
For questions or to compare routes against your existing flow, see About GhostSwap.
