Home / Blog / Hackers steal $23.7 million in crypto from Ostium in…
Tech News

Hackers steal $23.7 million in crypto from Ostium in off-chain attack

By Dillip Chowdary • Jul 21, 2026 • Source: BleepingComputer

According to a report from **BleepingComputer**, the **Ostium** trading platform announced that an attacker stole **$23.75 million** in cryptocurrency from its **liquidity provider vault** last week. The incident occurred after an unauthorized actor compromised the protocol's **off-chain infrastructure**.

The exploit targeted the system's external price-feeding mechanics rather than on-chain smart contract code. By breaching the **off-chain infrastructure** responsible for supplying price data into the protocol, the attacker manipulated price inputs to drain capital directly from the **liquidity provider vault**.

For system architects and engineers, this compromise illustrates the security risks associated with hybrid protocol designs. Even when on-chain vault contracts execute as intended, dependencies on external or **off-chain infrastructure** introduce critical vectors that can compromise the entire protocol.

In the broader market context, this attack highlights an ongoing challenge for trading platforms relying on external data feeds. As platforms like **Ostium** operate liquidity vaults, the security of off-chain pricing pipelines remains a pivotal exposure point for decentralized trading protocols handling substantial capital reserves.

The immediate technical takeaway for engineering teams is the necessity of securing off-chain data delivery channels alongside on-chain smart contracts. Moving forward, system operators will watch for updates from **Ostium** regarding infrastructure remediation and potential enhancements to their price-feed verification processes.

Advertisement

Tech Pulse Daily

Get tomorrow's pulse first

Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.

---

### Summary of Work

- Drafted a 5-paragraph analytical news article on the Ostium off-chain infrastructure breach.

- Structured the response according to the requested five criteria: event summary, technical mechanics, developer impact, market context, and practical takeaways.

- Used strictly the provided facts without inventing dates, version numbers, or unverified figures.

- Logged task status to local session task logs as required.

Advertisement

🔎 More interesting news

5-min tech signal

Weekday briefing for engineers who skip the noise.

No spam · Unsubscribe anytime

Advertisement

✈️ CareerPilot

Your AI job-search copilot

Match your resume against live Ashby, Greenhouse & Lever openings — fit scores, job-specific resume optimization and email alerts.

Find matching jobs →

Free Tools

Browse all tools →