BlackHart
Go live
Hacks feed/Ostium

Ostium

July 15, 2026·Arbitrum·Key Compromise
$23.8M
total loss
StatusConfirmed

Why it happened

Attack class: Access control

Stolen 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.

Trader marginsafe(stayed in the trading contracts)
Protocol multisigssafe
Other traders' positionssafe(fake prices only settled the attacker's orders)
Public OLP vaultdrained(23.75 million USDC paid out as fake profit)
Liquidity provider recoverypartially affected(small holders repaid in full; about $650,000 recovered so far)
Exploit anatomy

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.

The 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.

  1. Step 1: Root control

  2. Step 2: Fake prices

  3. Step 3: Cash out

    • Swap
      KyberSwap and about 30 wallets
      USDC to about 12,084 ether
      spread across fresh wallets
    • Exit
      Tornado Cash
      about 10,540 ether in
      by 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

1.
The attacker gained unauthorized access to Ostium's off-chain price infrastructure: the authority to produce signed price reports that the on-chain verifier accepts, and the operator account 0xD1794196f0fc99c7f27970e661597d77d9a85869 that drives Ostium's registered forwarder contract. Ostium has not published how that access was obtained.
2.
From the beneficiary wallet 0x321Df194646029e7A6193Ea05573d4B9c398bfD9, the attacker called setDelegate on the OstiumTrading contract so the registered forwarder could open and close trades on that account's behalf. This was an ordinary user-level delegation, not a new protocol role.
0x6D0bA1f9...702411setDelegate(address)
3.
At 14:18:23 UTC the operator account sent a batch through the forwarder that opened a 100 USDC BTC-USD position against a signed report priced at $5,000 and closed it against a second report priced at $60,000. The OLP vault paid about 897.8 USDC of artificial profit. This was the test cycle.
0xfE12F636...d5bd2EexecuteBatch(address[],bytes[])tx:0x4b7ff5de...d80951
4.
25 seconds later the main batch ran twenty calls, alternating trade calls to OstiumTrading with price deliveries to the OstiumPrivatePriceUpkeep contract, and repeated the open at $5,000, close at $60,000 cycle five times with growing collateral. The OLP vault paid 11,861,520 USDC to the beneficiary wallet in one transaction.
0xfE12F636...d5bd2EexecuteBatch(address[],bytes[])tx:0x359f8c05...4870e0
5.
Between 14:19:37 and 14:23:52 UTC the attacker ran six more standalone cycles of falling size. The last one brought the total paid out of the public OLP vault to 23,752,746 USDC, at which point the vault's circuit breaker blocked further withdrawals.
0xfE12F636...d5bd2EexecuteBatch(address[],bytes[])tx:0xfaf6d3d4...e8ba8c
6.
Ostium's monitoring and outside alerts flagged the activity. The first containment transaction landed at 14:55 UTC, 37 minutes after the test trade, and all trading contracts were frozen by 15:14 UTC. The compromised systems were deauthorized and isolated.
7.
The stolen USDC was swapped into about 12,084 ether, largely through KyberSwap, and spread across roughly 30 attacker-controlled wallets. PeckShield counted about 10,540 ether deposited into Tornado Cash by the end of the day. By late September Ostium reported 649,967 USDC recovered.

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

Bound every signed price against an independent reference feed.

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.

Split price signing and forwarder operation across independent, threshold-held keys.

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.

Cap vault payouts per account and per time window much lower.

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.

Reject reports whose timestamps do not fit the order and the current block.

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

Drift (2026)

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.

KiloEx (2025)

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

1.Ostium froze all trading contracts by 15:14 UTC, deauthorized and isolated the affected systems, and engaged SEAL 911, Mandiant, zeroShadow, Collisionless and law enforcement.
2.Ostium migrated to a new production environment with multi-party approvals for off-chain infrastructure, then reopened trading on July 23, 2026, marking positions to the live price at reopen.done
3.Ostium released a liquidity provider recovery plan in late September: 3,321 of 3,666 affected wallets, those with losses of 1,000 USDC or less, can claim in full, and larger holders are paid pro rata from recovered funds and a share of protocol revenue. Recovery of the full loss is pending.done
4.Perpetuals venues that use signed off-chain prices should add on-chain deviation checks against an independent feed and treat their signer and keeper infrastructure with the same custody discipline as their contract admin keys.

Timeline

2026-07-15Test cycle: a 100 USDC position opened at a signed $5,000 BTC price and closed at $60,000 pays about 897.8 USDC.
2026-07-15Main batch of five cycles pays 11,861,520 USDC from the OLP vault.
2026-07-15Sixth standalone cycle completes; total drained reaches 23,752,746 USDC and the vault circuit breaker blocks further withdrawals.
2026-07-15First on-chain containment transaction.
2026-07-15All trading smart contracts frozen. Blockaid has publicly flagged the drain and Ostium confirms it has paused trading.
2026-07-23Trading resumes in a migrated production environment.
2026-07-29Ostium publishes its post-mortem.
2026-09-30Liquidity provider recovery portal reported open; 649,967 USDC recovered from the attacker so far.
Blockaid (first public alert). Ostium (post-mortem). PeckShield (fund tracing). SEAL 911, Mandiant, zeroShadow, Collisionless and Inca Digital (response and tracing)
Continuous adversarial monitoring

Get your protocol scored across 12 dimensions, or request ongoing coverage.