$60M Gone in Minutes — and the Company Is Calling It a Feature, Not a Bug
One pre-market trade in Korea dropped a mark price 19% and triggered $60 million in crypto liquidations. The company behind the oracle that fed that price says everything worked exactly as designed.
Let that sink in.
What Actually Happened
A single low-liquidity pre-market trade in the Korean market moved a mark price by nearly a fifth. That price was picked up by the oracle, treated as gospel, and broadcast directly into positions held by traders who had no idea a thin, illiquid order was about to define their net worth.
The cascade that followed wiped $60 million in liquidations in what sources describe as a matter of minutes.
When the dust settled, the company announced it would cover all losses. That sounds like accountability. But read the fine print: they are not admitting the oracle failed. Their official position is that the system functioned precisely as intended.
Why That Distinction Matters Enormously
If this was a bug, you patch it. Traders get made whole, the protocol improves, and the market moves on.
If this was a feature, then every position you hold on any protocol using this oracle is exposed to the exact same risk right now. A single illiquid trade in a low-volume market, at the wrong hour, in the right jurisdiction, can reprice your entire position before you can blink.
Oracles are the invisible infrastructure of DeFi. Most traders never think about them until a moment exactly like this one. They sit between the real world and your on-chain positions, and when they ingest a bad price, they do not know it is bad. They just report what they see.
The question no one is asking loudly enough: how many other oracles are using similar methodology across protocols you are using today?
The Uncomfortable Truth About DeFi Liquidations
Liquidation events of this size are rarely random. They follow a pattern: low liquidity window, outsized single trade, oracle ingestion, cascading forced sells. It is a well-known attack vector. Whether this was deliberate manipulation or an organic market accident, the outcome for traders was identical.
The company covering losses does not change the structural vulnerability. It just makes this particular incident quieter.
What Traders Should Do Right Now
Pull up every leveraged position you hold and check which oracle is pricing it. If documentation is thin or the oracle sources pre-market or regional feeds, reduce exposure until you understand the risk. This story is not over. When a company calls a $60 million liquidation event a success, the only rational response is to treat your own risk management as if no one else is watching it for you.
Because right now, they are not.