Ostium Exploit: $23.75M Lost in Arbitrum Oracle Manipulation Incident

In just over five minutes, the Arbitrum-based perpetuals trading platform Ostium, which had recently announced support from General Catalyst, Jump Crypto, and a Nasdaq data integration, suffered a loss of $23.75 million due to a sophisticated attack exploiting its price oracle system.

The perpetrator bypassed smart contract vulnerabilities entirely, instead targeting Ostium’s proprietary price-reporting infrastructure to manipulate the vault’s perceived asset prices. By controlling the oracle's reports, the attacker was able to dictate pricing at will.

On the day of the incident, BTC's on-chain price was set to $5,000 for an opening trade, then immediately adjusted to $60,000 to close, a highly unrealistic twelvefold swing that only affected Ostium’s internal records, not the actual crypto markets.

The attacker leveraged this mechanism to repeatedly place and settle trades against the OLP vault, draining its liquidity within a brief five-and-a-half-minute period. Liquidity providers, who had expected to earn yield, instead saw their funds used to cover the exploit’s artificial profits to the last cent.

The exploited functionality was not an unknown weakness. Ostium had explicitly documented this area in their bug bounty scope, but specifically excluded it from researcher scrutiny.

The stolen assets were quickly funneled through Kyber and then obfuscated via Tornado Cash before most security firms could even determine the total loss.

This breach prompts the question of whether an incident counts as a break-in if the vulnerability was both known and off-limits for review.

Detection and Community Response

Blockaid’s monitoring system detected the exploit as it was underway on July 15, identifying the attacker's wallet and transaction before the process was complete: “An attacker used a registered PriceUpKeep forwarder and future-dated authorized oracle reports to create artificial trade profit, triggering a ~$18M USDC payout from the vault.”

Shortly after, RogueTrader reported the higher loss of $23.75 million and provided the exploit address.

Cyvers tracked the laundering process, which involved bridging funds through ChangeNOW, swapping USDC to ETH on Arbitrum, and distributing the assets among attacker-controlled wallets.

Ostium issued a public announcement soon after Blockaid’s alert: “We are aware of the issue with the OLP vault. We have paused all trading. The team is investigating.”

A subsequent update stated: “Trading remains paused following the security incident. User positions remain open and unmodifiable, and trader margin remains unmoved in frozen trading smart contracts. Over the past 14 hours, the team has been in continuous coordination with relevant authorities, SEAL 911, and multiple security researchers.” (source)

Ostium’s founder, kaledora, provided additional details later that day: “This morning, between 14:18-14:23 UTC, Ostium experienced a security issue leading to a loss of funds from the public OLP vault. Our team identified the issue within minutes and immediately began taking steps to contain it, including coordinating to pause trading contracts within the hour.”

The incident drew criticism, with CBB remarking: “Maybe next time focus on securing your protocol instead of trying to beef with Hyperliquid.”

QuillAudits provided a technical breakdown, confirming that the attacker started a leveraged trade, called the price upkeep function in the same transaction, and successfully submitted a report signed by a trusted address.

By the time full asset tracing was completed by PeckShield and Lookonchain (additional trace), the funds had already been converted to 12,084 ETH and deposited into Tornado Cash. Investigators reconstructed the exploit path before Ostium released a final loss figure.

Technical Root Cause: Oracle Manipulation via Trusted Forwarder

Traditional data sources for gold, forex, and equity indices are not available on-chain. Ostium addressed this by building a pull-based oracle: prices are written to the blockchain only when needed for trade settlements, delivered through the Gelato automation network, which Ostium’s documentation designates as the sole authorized initiator.

Ostium’s audit scope references two contracts: PriceUpKeep and PrivatePriceUpKeep. The exploited deployment was PrivatePriceUpKeep, confirmed by event logs and internal call traces. The public PriceUpKeep contract was not involved in the exploit.

The Registry contract pointed to the current verifier address since a governance update on February 14, 2026, which also added four authorized signers, including the address identified by QuillAudits as used in the exploit.

The attack required two elements: a registered PrivatePriceUpKeep forwarder capable of submitting prices, and a price report that passed signature verification using an authorized key (technical trace).

A single executeBatch call in the exploit triggered 20 internal contract calls, alternating between the Trading contract and PrivatePriceUpKeep, and repeating the open/close process five times. All trades targeted pairIndex 0 (BTC/USD), with a feed hash matching the exploit’s price events.

The manipulated trade opened at exactly $5,000 and closed at about $60,000—a move not possible on real markets.

In essence, the protocol trusted a price report from an authorized forwarder without independent validation, allowing the attacker to extract millions based on a falsified price. The underlying issue was not a forged signature or contract malfunction, but a trust assumption in the system’s architecture.

Ostium’s bug bounty documentation classified registered keepers and their forwarders as “assumed to be trusted and operating correctly,” excluding compromised keeper scenarios from reward eligibility. The exploit thus leveraged a path that had been purposely omitted from external review.

Attack Flow: From USDC to ETH via Kyber and Tornado Cash

The breach spanned eight transactions over five minutes and 29 seconds, starting with a $100 test loop that netted an $897.80 payout, followed 25 seconds later by a major transaction extracting $11.86 million in one batch. Six further transactions withdrew the remaining funds, leaving the vault nearly empty.

All proceeds were quickly converted from USDC to 12,084 ETH via KyberSwap and dispersed to 30 addresses controlled by the attacker. PeckShield observed 10,540 ETH sent to Tornado Cash on the same day. The originating wallet had been seeded with small deposits from ChangeNOW and Bybit.

Arkham’s analytics show discrepancies in volume due to double-counting trades, but the majority of funds were confirmed as laundered.

Key Addresses and Transactions:

• Attacker: 0x321Df194646029e7A6193Ea05573d4B9c398bfD9
• Test Transaction: 0x4b7ff5de823dd7af29cf1a6602a84d7b6eee354edcbaf0427fd5e691d3d80951
• Main Exploit: 0x359f8c05b86a4409d60cfba02084334313fd94b19f74a294fb7fc4ea7d4870e0
• OLP Vault: 0x20D419a8e12C45f88fDA7c5760bb6923Cee27F98
• PrivatePriceUpKeep (exploited): 0xB71ec9eBD8145daCaCF6724363143cb5667A3d36

Security Review History and Audit Trail

Ostium underwent six audits by three firms between 2024 and 2026 (audit documentation).

• Zellic completed a pre-mainnet review in February 2024, identifying 19 issues (2 critical).
• ThreeSigma followed in March, noting 57 findings (one critical, two high severity).
• Pashov Audit Group conducted reviews in January and April 2025, and again in January 2026.
• A second engagement by Zellic occurred in late 2025.

Ostium’s public summaries downplayed the critical findings, though the original reports documented significant risks (e.g., collateral manipulation, order ID reuse).

Zellic’s scope explicitly excluded off-chain infrastructure and key management. Auditors flagged the forwarder mechanism as a risk but did not fully analyze it, as this was not in scope.

After Zellic’s November 2025 review, a section specifically highlighted the possibility of a compromised forwarder causing harm: “By design, forwarders can cancel any order or action... These concerns are not a complete enumeration of the potential issues that can arise from a compromised forwarder.” (report section)

Ostium addressed only the example exploit given by Zellic, leaving the broader risk unaddressed and out of scope for future audits or the bug bounty program.

Official Response and Recovery Plans

Ostium’s incident playbook included pausing all trading, freezing positions, and working with security partners and authorities. Updates confirmed that user positions remained frozen and that a recovery plan for liquidity providers was forthcoming, potentially involving Ostium’s own resources and new partnerships. (status update)

A technical post-mortem and reimbursement plan were still pending at the time of writing. Ostium confirmed the attack involved compromised off-chain infrastructure that submitted manipulated but formally valid price reports, enabling the rapid extraction of funds.

Conclusion

The Ostium exploit was not the result of an overlooked smart contract bug, but rather a risk that had been identified, documented, and deliberately excluded from further scrutiny.

Despite extensive auditing by multiple firms, the architectural trust placed in keepers and forwarders was never independently validated for compromise scenarios. This gap ultimately enabled the manipulation that led to $23.75 million in losses.

While Ostium’s size and backers may help the protocol survive, the incident highlights the importance of clear audit scope, comprehensive bug bounty coverage, and acting on warnings when they are raised—not just patching specific examples, but addressing the underlying systemic risk.

References: The Block, Rogue Trader, Blockaid, defiprime, QuillAudits, kaledora, ImmuneFi, Peckshield, Cyvers, Ostium, CBB, Lookonchain, CoinTelegraph, evm codes, Zellic, ThreeSigma, Pashov Audit Group, DefiLlama