Ostium Loses $24M in 5 Minutes Due to Oracle Manipulation Using 'Future' Price Data

Author: CryptoSlate

Compiled by Deep潮 TechFlow

Shenchao Summary: This is not a missing signature, but an authorized signer submitted price data "from the future." When validation passes but the data itself is toxic, where is the moat of DeFi protocols? Ostium has yet to disclose its final loss assessment or post-incident report, leaving significant questions about the abuse of signer permissions.

The on-chain perpetual trading platform Ostium reported that a five-minute security incident resulted in a loss to its public liquidity vault. Security firms estimate the scale of the vulnerability at up to $24 million.

Co-founder Kaledora Kiernan-Linn confirmed that the issue occurred between 14:18 and 14:23 UTC on July 15, affecting the public Ostium Liquidity Provider (OLP) treasury. She stated that the team identified the issue within minutes and coordinated a trading pause within one hour. The statement did not provide the exact total loss, root cause, or final post-incident report.

Security firms stated that the core of the incident involved authorized data, not missing signatures. Blockaid and Cyvers said a registered PriceUpKeep relayer submitted an authorized oracle report with a future date, creating false transaction profits.

SlowMist stated that the authorized signers provided manipulated data with valid signatures to enable repeated profitable transactions. These findings are still based on third-party discoveries and await confirmation through Ostium’s post-incident report.

Cryptography authentication confirms that the report was signed by an authorized key. However, price reasonableness, timestamp freshness, and settlement security require separate control measures.

The OstiumVerifier code from the Ostium secure document link recovers the ECDSA signer and checks whether the signer is authorized, but this verification function does not enforce price sanity checks or timestamp boundaries.

The code does not appear to indicate which implementation version is active during the event, or whether separate contracts apply these checks. Any timestamp, replay, price deviation, or multi-source protection measures must be executed elsewhere in the execution path.

Ostium’s protocol documentation states that the OLP vault holds traders' collateral and makes instant on-chain payments to winning trades. If false profits are accepted for settlement, the vault’s liquidity covers these payments.

The estimated public figures have continued to rise as tracking progresses. Blockaid believes the payment was close to $18 million, Cyvers estimates $23.7 million, and PeckShield later described approximately $24 million being drained.

SlowMist’s lower figure of $11.86 million appears to track a treasury outflow of 11,862,444.782 USDC visible in its cited transactions.

PeckShield stated that the withdrawn USDC was exchanged for 12,080 ETH, and as of its update, 10,540 ETH had been sent to Tornado Cash. Kiernan-Linn said Ostium is collaborating with law enforcement, SEAL 911, and third-party security experts.

This mechanism distinguishes Ostium from a similar issue that occurred with Hedera’s loan protocol, Bonzo Lend, four days ago. The Bonzo incident report stated that its validator accepted a proof lacking a valid signature. In the Ostium case, the security firm claimed the report passed through the authorized signer path: authentication succeeded, but the data was allegedly insecure.

Ostium still needs to confirm whether the signer key has been compromised, whether authorized operators engaged in malicious behavior, or whether other privileged pathways have been abused.

Its remediation measures—including signer isolation, strict timestamp boundaries, independent price checks, rate limiting, and circuit breakers—will be evaluated on whether they can prevent a trusted path from turning minutes of bad data into another vault payment.