Ostium
Why it happened
Attack class: Access controlStolen off-chain authority signed BTC prices of $5,000 and $60,000.
What would have stopped it
- Bound every signed price against an independent reference feed.
- Split price signing and forwarder operation across independent, threshold-held keys.
Not scored before the exploit
BlackHart had not scored Ostium before this exploit.
An attacker who broke into Ostium's off-chain price system on Arbitrum used it to feed the exchange fake Bitcoin prices, opening trades at $5,000 and closing them at $60,000 within the same transaction. Each round trip booked a fake profit that Ostium's public liquidity vault paid out in real money, and eight transactions in five and a half minutes took 23.75 million USDC. Trader margin and the protocol's multisigs were not touched; the loss fell on the vault's liquidity providers. The USDC was swapped to ether and much of it went through Tornado Cash, and Ostium has since recovered about $650,000 and opened a recovery plan for liquidity providers.
Using a compromised operator account and Ostium's own registered forwarder, the attacker delivered signed BTC prices of $5,000 and $60,000 for trades on its beneficiary wallet, and the OLP vault paid the fake profit, 11.86 million USDC in the main batch alone.
Attack flow
All 7 on-chain stepsThe attack in 3 steps. Step 1, Root control: OLP vault (source). Step 2, Fake prices: Registered forwarder (hub), Beneficiary wallet (hub), about $23.75M reached this step. Step 3, Cash out: KyberSwap and about 30 wallets (swap), Tornado Cash (exit), about $23.1M reached this step.
Step 1: Root control
- SourceOLP vaultpays trader profit in USDCabout $63M before the attack0x20D419a8...e27F98
Step 2: Fake prices
- HubRegistered forwarderopen at $5,000, close at $60,0008 transactions, 14:18 to 14:23 UTC0xfE12F636...d5bd2E
- HubBeneficiary walletreceives the fake profit23.75M USDC0x321Df194...98bfD9
Step 3: Cash out
- SwapKyberSwap and about 30 walletsUSDC to about 12,084 etherspread across fresh wallets
- ExitTornado Cashabout 10,540 ether inby the end of July 15
Why each step worked
- Off-chain price infrastructure breachedprice signing authority in the attacker's hands
- Compromised forwarder operator account0xD1794196f0fc99c7f27970e661597d77d9a85869
- No check against a market referencemissing controlthe verifier only confirms an authorized signer, not a plausible price
- Circuit breaker set too loosemissing controltripped only after about 28 percent of the vault had left
- No outflow hold on fresh profitmissing controlsame-transaction profit could leave the vault at once
Full forensic detail
Step-by-step reconstruction, root cause, counterfactuals, remediation, and disclosure timeline.
Exploit anatomy
setDelegate(address)Root cause
Ostium settles trades with a pull-based price system: an off-chain service produces a signed price report, a registered forwarder submits it on-chain, and the OstiumPrivatePriceUpkeep contract accepts it after checking that the caller is a registered forwarder, that the order exists, and that the report's signature recovers to an address marked as an authorized signer. The trader's profit is then paid from the public OLP liquidity vault. Those checks prove who sent a price, not whether the price is true. Nothing on-chain compared a report with an independent market reference or bounded how far it could move, and the report's timing values were chosen by whoever produced it. So once the attacker held the off-chain authorities that sign reports and operate the forwarder, they could open a BTC-USD position at a signed $5,000 and close it at a signed $60,000 in the same transaction, and the vault paid the difference as real USDC. No smart contract was broken and no flash loan or market capital was needed. Ostium's post-mortem says the initial access was off-chain and that it found no vulnerability in its contract logic and no compromise of the multisigs that govern the protocol. Per Rekt, a late-2025 Zellic review had already warned that a compromised forwarder can act with full trust, and the bug bounty scope treated registered keepers and forwarders as trusted. The vault circuit breaker eventually stopped the drain, but only after about 28 percent of the roughly $63 million vault had left.
Prevention analysis
A BTC-USD report at $5,000 while the market traded near $60,000 is off by more than 90 percent. A deviation check against a second, independently run oracle would have rejected the first fake report, and the attack would have stopped at the 100 USDC test.
The attack needed both the authority to sign prices and the account that submits them. Holding these in separate hardware-backed or multi-party custody means one breach of the off-chain stack no longer yields both, which is the direction Ostium took with multi-party approvals in its new production environment.
The circuit breaker worked, but only after about $23.75 million had left in five and a half minutes. A per-account profit cap or a smaller rolling withdrawal limit would have held the loss to a fraction of that while the team responded.
The fake reports carried timing values the attacker picked. Requiring a report to be fresh relative to the block and later than the order it settles narrows what a stolen signer can do.
Similar incidents
Privileged authority was taken over off-chain, then used to feed the protocol a fake value it trusted and withdraw real funds in minutes. In both cases the contracts behaved as written; the trust placed in a key or role was the weak point.
A perpetuals exchange accepted attacker-chosen prices through a trusted forwarder path, letting positions open at a fake low price and close at a fake high price against the protocol's liquidity.
Remediation
Timeline
Get your protocol scored across 12 dimensions, or request ongoing coverage.