Balance Coin Crashes 99% After $915K 42DAO Oracle Exploit

42DAO’s BTCB Oracle Failure Triggered BLC Liquidations

42DAO describes itself as the governance body behind Balance Protocol, which it says issues the USD-pegged Balance Coin. Its official site says the system uses a buffer pool and collateralized components to support BLC, a design that depends on price inputs to determine when a vault should be liquidated.

Those inputs became the reported point of failure. Crypto Adventure said an unusually low BTCB value was accepted through the Median Oracle and written into the protocol before the liquidation process began. In plain language, collateral that was worth more at the real market price was treated as though it had suddenly lost most of its value.

Liquidation is meant to protect a collateral-backed stablecoin by closing unsafe positions before debt becomes unbacked. When the price signal is false, the same mechanism can force legitimate vaults into liquidation and create a gap between issued tokens and the assets meant to support them.

The report said the protocol did not impose a price-deviation limit, a minimum price or a delay before processing the update. 42DAO has not confirmed that technical description in a public incident report, so it remains an account of the observed exploit rather than a final root-cause finding.

The case arrives days after Bonzo Lend paused after a separate oracle-verifier failure. The networks, assets and code paths differ, but both episodes show how an external price dependency can convert a small input error into a much larger credit and liquidity event.

BLC Depeg Deepened as New Supply Hit PancakeSwap

The reported attack did not stop at a false price. The larger of two suspicious transactions minted about 4.5 million BLC and routed it into PancakeSwap V2 liquidity, according to Crypto Adventure. The attacker then swapped the new supply for BSC-USD and BTCB, while a later transaction reportedly minted a further 5,900 BLC and removed additional assets.

That sequence helps explain why a loss estimated under $1 million could produce a far larger percentage move in BLC. A stablecoin’s peg relies not only on the value of backing assets but also on credible redemption, liquidity and the expectation that supply cannot be created without sufficient collateral. Once traders saw a sudden supply shock in shallow pools, selling pressure had little visible support underneath it.

The BLC contract page on BscScan identifies the token and its BNB Smart Chain address, but a token contract by itself does not explain which protocol rules authorized minting or whether the affected balances can be restored. Those questions require a full accounting from the protocol or independent on-chain analysis.

There is a useful comparison with the Ostium vault incident, where a reported price-manipulation path also turned a trusted market input into a loss. BLC’s event was smaller in dollar terms but more immediately visible to holders because the token’s stated purpose was to stay near one dollar.

The market snapshot is therefore a depeg, not evidence of a completed recovery. Reports tracked prices below one cent after the attack, and no official plan had established a conversion value, new collateral commitment or mechanism to restore BLC’s dollar target.

42DAO Has Not Released a BLC Recovery Plan

42DAO’s website continued to present BLC as the ecosystem’s stablecoin, while its public documentation describes the buffer pool as a reserve that accumulates liquidation penalties. Neither source, at the time of review, provided an incident-specific statement explaining the affected vaults, remaining assets, emergency controls or what BLC holders should expect.

That absence is material because a stablecoin incident has two separate stages. Containment stops the immediate exploit path. Resolution then requires a transparent balance sheet, a clear legal or governance process, and a decision about whether holders, liquidity providers, debt positions or the protocol treasury absorb the loss. None of those outcomes can be assumed from an initial security alert.

It also means users should be cautious about unofficial recovery messages. A fast-moving exploit often attracts impersonation attempts, especially when the legitimate team has not yet published instructions. Holders can independently verify the BLC address through BscScan, but should not approve a transaction or sign a message solely because it is framed as a reimbursement claim.

The next concrete checkpoints are an official 42DAO statement, a transaction-by-transaction estimate of assets removed, a review of the oracle and liquidation controls, and any governance proposal addressing BLC’s outstanding supply. Until then, the confirmed market fact is the scale of the depeg; the path to recovery remains undisclosed.