Hyperliquid Faces $57 Million Liquidation Event After SK Hynix Oracle Error

A bad price print in South Korea hit Hyperliquid’s SK Hynix perpetual and triggered $57.4 million in liquidations. The incident is putting external oracles and HIP-3 risk controls in DeFi under the spotlight.

Key Takeaways

• Hyperliquid’s SK Hynix perpetual fell 17.9% on Tuesday after a bad price print in Seoul.
• About $57.4 million in long positions was liquidated across 960 accounts.
• The error came through an external oracle source; Trade.xyz runs the market under HIP-3 and has not published a post-mortem yet.

Hyperliquid’s SK Hynix perpetual contract, xyz:SKHYNIX, fell 17.9% on Tuesday after a faulty price print in Seoul. The move wiped out roughly $57.4 million (€50.4 million) in long positions across 960 accounts. It’s a sharp reminder of how exposed perpetual markets can be when they rely on an outside price source that sends in a distorted reference.

What Went Wrong

The problem started with NXT, a South Korean alternative exchange that went live in March 2025 and trades from 8:00 a.m. to 8:00 p.m. local time. By comparison, the Korea Exchange only operates from 9:00 a.m. to 3:30 p.m. Those extra hours tend to be thinly traded, which makes the reference price much easier to move if a bad order slips through.

Based on the trading data available, SK Hynix was marked at 1,272,000 won in pre-market trading. That number has not been confirmed by the parties involved, but it was still far below the previous session’s close of 1,785,000 won. On paper, that implied a 28.7% drop, after which trading in Korea was halted.

Why the Drop Stayed Smaller

The market design helped limit the damage somewhat. Hyperliquid did not create or operate this market itself. Trade.xyz did, using HIP-3, a framework that lets independent teams launch their own perpetual markets and set details such as oracle sources. The oracle for xyz:SKHYNIX pulls prices from outside venues while they are open and converts won into dollars at the current exchange rate.

Trade.xyz also relies on discovery bounds, which are meant to keep the mark price from drifting too far. For xyz:SKHYNIX, the setup includes an immediate 10% band and one allowed reset, creating a hard floor at 19% below the session reference. The reported 17.9% decline stayed just within that range. On-chain analysis suggests 960 long accounts were closed and about $17.3 million (€15.2 million) in realized losses were recorded, while the backstop mechanism auto-deleveraged profitable shorts. Hyperliquid and Trade.xyz have not confirmed those figures.

What This Says About Hyperliquid

The episode raises a broader DeFi question: what happens when a protocol depends on external price feeds and one bad data point moves the entire market? In this case, it also matters that Hyperliquid uses cross margin for this market, which means losses on one position can spill over into the collateral backing other positions. That can accelerate liquidations if the underlying price feed moves suddenly.

For European crypto readers, the takeaway is that HIP-3 shows how much control decentralized infrastructure can hand to third parties. At the same time, the incident makes clear that oracle sources and risk settings still matter, even when a market runs onchain. Trade.xyz has not released a post-mortem or compensation plan yet, while validators do have a slashing mechanism for deployers who stake 500,000 HYPE.