Loading market data...

Single Trade on South Korean Exchange Triggers $57M Liquidation Cascade on Hyperliquid

Single Trade on South Korean Exchange Triggers $57M Liquidation Cascade on Hyperliquid

A single share trade on South Korea's Nextrade exchange sent the SKHYNIX perpetual on Hyperliquid crashing about 20% in seconds, wiping out $57 million in positions. The trade, placed 30% below the previous closing price during pre-market at 11:00 pm UTC on July 27, 2026, briefly set the price on Nextrade due to thin liquidity — and Hyperliquid's oracle swallowed the bad data within four seconds.

How a single trade caused a 20% drop

The SKHYNIX perpetual dropped from $1,131 to as low as $900 instantly. The XYZ oracle, which feeds price data to Hyperliquid, consumed the erroneous Nextrade price within four seconds of the exchange opening, causing a 15.6% drop in the oracle price. That was enough to trigger a cascade of liquidations. The trade itself may have been accidental, but the damage was real.

Liquidations and auto-deleveraging

Liquidations began about two seconds after the oracle price dropped. In total, 960 accounts were liquidated, with $57 million in positions wiped out. Realized losses from the cascade hit $17.3 million. Auto-deleveraging then kicked in against profitable short positions, transferring $10.8 million in gains across 100 accounts. The largest single gain was $2.55 million; the largest single loss was $2.05 million.

Mimicking a real market correction

The flash crash on Hyperliquid closely mirrored a real stock price correction of roughly 15% that occurred hours later on the open market. The timing suggests the erroneous trade on Nextrade may have been a precursor to broader market moves, though the connection remains unclear. Hyperliquid is a permissionless exchange, meaning no central authority can halt trading or reverse transactions.

XYZ investigation ongoing

The SKHYNIX perpetual is deployed and operated by XYZ, which is investigating the incident but has not released a statement. Questions remain about how the oracle handled the outlier price and whether any safeguards could have prevented the cascade. For now, the 960 affected accounts are left waiting for answers.