The perpetual contract for shares of South Korean giant SK Hynix (ticker xyz:SKHYNIX) on the Hyperliquid platform experienced a sharp 17.9% drop followed by a rapid recovery. The cause was an anomalous pre-market trade that triggered a chain reaction in the decentralized market.
The incident occurred on NXT, an alternative trading venue in South Korea, where one share of SK Hynix was sold at 1.272 million won. This movement was approximately 30% and caused a trading halt for the stock. However, the consequences were not limited to the traditional market — Hyperliquid's oracle transmitted this drop to the network, leading to a collapse in the derivative.
Mechanism of the Collapse: The Role of Oracles and Arbitrage
The xyz:SKHYNIX contract tracks the price of the underlying asset through an oracle — a service that supplies external quotes to the blockchain. When a sharp spike occurred on NXT, the oracle recorded the new price, and the contract on Hyperliquid crashed in response. Arbitrageurs on Binance also began selling, attempting to profit from the price difference, which intensified the pressure. However, the market soon recovered, returning to previous levels.
Who Controls the Market: The Deployer, Not the Platform
An important nuance: the xyz:SKHYNIX contract is launched and maintained by a third-party team, XYZ, not by Hyperliquid itself. A Hyperliquid team member under the nickname iliensinc explained that they are investigating the incident and will report the results. This highlights Hyperliquid's architecture as an infrastructure layer — anyone can launch their own market, but responsibility for its settings and price parameters falls on the creator (deployer).
How the Mark Price is Formed
According to the HIP-3 standard, the deployer themselves provides the platform with the execution price, oracle data, and external quotes. The key parameter is the mark price, which is used to calculate profits, losses, and forced liquidations. It is derived as the median of three values: one is provided by the protocol (median of the last trade, best bid, and best ask), and two are provided by the deployer. If the protocol shows 100, and the deployer provides 150 and 151, the mark price becomes 150. Thus, the market operator can shift the calculated price even when the platform's own data indicates a different level.
Expert opinion: This incident is a vivid example of how vulnerabilities in decentralized financial systems can be caused not only by technical glitches but also by human factors. Dependence on oracles and the deployer's ability to influence the mark price create risks for traders, especially in markets with low liquidity. In the future, a more transparent system for validating such price data will likely be needed.