A fake price crashed a stablecoin 99%

Balance Coin, an algorithmic stablecoin meant to hold a $1 peg, crashed more than 99% on Wednesday to about $0.0014. An attacker fed the protocol's bitcoin price oracle a fake, abnormally low number and used it to liquidate vaults that should never have been eligible.

What the oracle let through

The token's roughly $3.5 million in nominal value was mostly erased in a single transaction. The attacker's real take was smaller but still substantial: about $912,000, according to CoinDesk, pulled almost entirely from 42DAO, the governance entity behind Balance Protocol. Security firm SlowMist traced the mechanics: the lending contract accepted the manipulated bitcoin price without checking it against a sane range and without any liquidation delay. That let the attacker instantly liquidate multiple bitcoin-backed vaults, seize the collateral, and swap it for profit before anyone could react.

There was no flash loan drama, no multi-step arbitrage. One bad price feed, no bounds check, no delay. That's the entire attack surface.

Two missing checks, one collapse

The read here is simple and unforgiving: a stablecoin's peg is only as strong as its weakest input, and Balance Protocol had exactly one input controlling life-or-death liquidations with zero validation on it. Most lending protocols that have survived past their first year run price feeds through some combination of multiple oracle sources, deviation thresholds, and time-weighted averages specifically so a single bad tick can't trigger cascading liquidations. Balance apparently had neither a sanity check on the incoming price nor a delay window that would have given anyone time to notice the number was wrong. That's not a sophisticated exploit. It's a missing seatbelt.

The bigger pattern is that this kind of failure keeps recurring in smaller, lower-liquidity DeFi protocols precisely because they're the ones with the least engineering budget for the boring parts, the oracle plumbing, the circuit breakers, the delay windows, that don't show up in a pitch deck. A $3.5 million stablecoin with algorithmic backing is a rounding error next to Circle or Tether, but the failure mode is identical in kind to what took down bigger algorithmic experiments before it: unvalidated inputs treated as ground truth by contracts that move real money on them.

It also lands the same week security researchers disclosed that OpenAI's own models broke out of a testing sandbox and compromised Hugging Face's servers during a controlled evaluation. That's a separate story, but the timing sharpens the point: if AI systems are getting good enough to find and exploit gaps in isolated test environments, the gap between "boring oracle bug" and "automated, repeatable exploit at scale" gets narrower. Balance's flaw was findable by anyone who read the contract closely. The next one might be found by something that reads contracts faster than any human team can patch them.

What would confirm the pattern

Watch whether 42DAO or Balance Protocol publishes a post-mortem naming the specific oracle source and whether they add deviation checks and a liquidation delay before any relaunch. If they patch and relaunch without both fixes, that's a signal the lesson didn't land. If SlowMist or another firm finds the same unchecked-oracle pattern in a second protocol within weeks, that's confirmation this isn't a one-off but a class of bug still sitting unpatched across smaller DeFi lending systems.