Speculation over Claude-assisted code emerges after Moonwell oracle glitch causes $1.8m loss.
A pricing error tied to an oracle configuration glitch left DeFi lending protocol Moonwell with roughly $1.8 million in bad debt after Coinbase Wrapped ETH (cbETH) was briefly mispriced at around $1 instead of reflecting its value relative to ETH.
The protocol, which operates on Base and Optimism, said the incident was triggered following the execution of a governance proposal that enabled Chainlink OEV wrapper contracts.
According to Moonwell’s post, one price feed was misconfigured in a way that caused the system to read an exchange-rate value without correctly applying the ETH/USD price. As a result, cbETH’s dollar valuation collapsed on-chain, even though the underlying asset had not moved in the broader market.
Liquidation Cascade Hits Borrowers Hard
The incorrect pricing quickly propagated through the protocol’s lending markets, where automated liquidators and bots reacted within minutes. Because collateral values appeared to plunge, borrower health factors deteriorated almost instantly, triggering a wave of forced liquidations.
Liquidators were able to repay small portions of outstanding debt and seize cbETH collateral at a deep discount, a mechanism inherent to DeFi liquidation logic when positions fall below collateral thresholds.
Approximately 1,096 cbETH was effectively lost during the cascade, translating into an estimated $1.78-$1.8 million shortfall for the protocol.
Moonwell’s risk manager, Anthias Labs, moved to contain the fallout by reducing supply and borrow caps on the affected market to near-zero levels, aiming to prevent new borrowing or deposits under the faulty configuration.
The team said the incident was isolated to the cbETH core market on Base and did not impact other markets.
Governance Decisions and AI Coding Questions
The episode highlights a persistent risk in DeFi infrastructure: operational failures in oracle integrations can generate protocol-level losses even in the absence of an external exploit.
In this case, governance execution and deployment timing appear to have played a key role, as fixes could not be implemented instantly due to governance and timelock constraints while liquidations were already underway.
Speculation Over AI-Assisted Code Raises Questions
The incident has drawn scrutiny after reports suggested that the faulty implementation may have involved AI-assisted development tools, including references to code allegedly co-authored with Claude.
While this claim has circulated in industry commentary, there is no conclusive public evidence establishing that AI involvement directly caused the bug.
Stay in the loop with DailyCoin’s hottest crypto news:
Cardano Price Compresses: Pump Phase Loading For $3 ADA?
Is Pi Coin’s Stellar Roots Enough To Push PI Back To $0.46?
