Bad Oracle Price Triggers $57.4M in Liquidations on Hyperliquid!

​The fragility of decentralized perpetual markets was on full display today. A single erroneous data point caused a massive flash crash on the decentralized exchange Hyperliquid, wiping out hundreds of traders and raising serious questions about oracle security in DeFi.
​
​The Bad Print
The chaos started when an off-chain data provider pulled a faulty pre-market price for SK Hynix from NXT, a South Korean trading venue. The erroneous order valued a single share at just 1,272,000 won implying a sudden 28.7% collapse in the stock's value.

​The Wipeout
The oracle fed this incorrect data directly into Hyperliquid's risk engine. As a result, the xyz:SKHYNIX perpetual contract instantly cratered by 17.9%. This sudden, artificial drop triggered forced liquidations on underwater long positions, wiping out roughly $57.4 million across 960 accounts.

​Contagion Risk
Due to the platform's cross-margin design, the damage wasn't contained to just the SK Hynix market. As traders' margins were depleted by the sudden drop, it amplified contagion risks across other positions.

​ Hyperliquid’s Response & Who is at Fault?

​Not Hyperliquid's Market: Hyperliquid quickly clarified that they neither deployed nor operated the specific SK Hynix market. Instead, the market was deployed by an entity called Trade xyz under the "HIP-3" framework.

​The Price Bounds: Trade xyz’s predefined discovery bounds (which included a 10% instantaneous bound and a ~19% floor) actually limited the flash crash to 17.9%, preventing the full 28.7% implied drop from hitting the order book.

​The Penalty: Because Trade xyz deployed the market, they are the ones responsible for the faulty feed. Under protocol rules, the deployer's 500,000 HYPE stake (worth roughly $27.4 million) is now slashable. However, this slashed HYPE will likely be burned rather than redistributed to the affected traders. Following the incident, the native HYPE token traded down roughly 9%.