Thorchain — disclosed vulnerability reports and payouts
Every publicly disclosed and closed bug bounty report we hold for Thorchain, with our own summary of each finding and a link to the original disclosure.
- Reports indexed
- 4
- Total paid
- $0
- Critical
- 0
- Largest payout
- $0
This page collects the 4 closed, publicly disclosed Thorchain reports indexed on Coin Buggie. Nothing here is active or unpatched — every entry was published by the programme or the researcher after remediation.
The findings concentrate in Integer overflow / underflow, Front-running / MEV, Reentrancy, across EVM-Solidity. Reading a single protocol end to end is the fastest way to see which assumptions its codebase repeatedly gets wrong, which is usually a better predictor of where the next finding lives than the category alone.
Use the vulnerability class links below to compare these findings against the same bug class in other protocols.
What reviewers look for
- Integer overflow / underflow findings disclosed against Thorchain
- Front-running / MEV findings disclosed against Thorchain
- Reentrancy findings disclosed against Thorchain
Curated highlights
The largest disclosed payouts in this group, with our own summary of each. Every report links back to the original disclosure.
Thorchain: Incorrect call argument in `THORChain_Router::_transferOutAndCallV5`, leading to grief/steal of `THORChain_Aggregator`'s funds or DoS
THORChain's router handles fee-on-transfer tokens incorrectly by assuming the full amount sent is received by the target. When such a token is transferred to the THORChain_Aggregator, a portion of the tokens is deducted as a fee, resulting in the aggregator receiving less than the specified amount. Subsequent logic in the aggregator fails because it relies on the original, incorrect amount, leading to transaction reverts or potential exploitation of existing funds held by the aggregator. This creates a Denial of Service for specific token swaps or exposes the aggregator's liquidity to manipulation.
Thorchain: A malicious user can steal money out of the vault and other users
The THORChain router protocol is vulnerable to fund theft when interacting with rebasing tokens such as AMPL due to incorrect accounting of token balances. The protocol relies on fixed allowance values recorded at the time of deposit; however, rebasing tokens change their supply dynamically, causing the contract's effective balance to deviate from the recorded allowance. A malicious user can exploit this mismatch by front-running rebase events to extract excess funds from the vault or other users via a malicious router contract.
Thorchain: ThorChain will be informed wrongly about the unsuccessful ETH transfers due to the incorrect events emissions
The THORChain Router contract incorrectly emits 'TransferOut' events for native ETH transfers, even when those transfers fail. When a recipient contract rejects incoming ETH, the router initiates a refund to the source vault but still logs an event stating the funds were delivered to the intended recipient. This discrepancy misleads off-chain monitoring systems, causing critical desynchronization between the protocol's actual on-chain state and its reported cross-chain activity.
Thorchain: Due to the use of `msg.value` in for loop, anyone can drain all the funds from the `THORChain_Router` contract
The THORChain router contract contains a critical logic error in its batch transfer functionality that allows an attacker to drain all native currency held by the contract. The issue stems from the improper use of `msg.value` within a loop, which causes the full transaction value to be sent to an attacker-controlled target multiple times during a single call. By providing a specially crafted array, an attacker can extract funds far exceeding their initial deposit, leading to complete fund loss for the protocol.