BTCC / BTCC Square / Cryptopolitan /
Claude Opus 4.6 Takes Heat After Moonwell’s $1.78M Exploit—AI’s Crypto Security Promise Cracks

Claude Opus 4.6 Takes Heat After Moonwell’s $1.78M Exploit—AI’s Crypto Security Promise Cracks

Published:
2026-02-18 12:24:28
19
3

Another day, another crypto exploit—only this time, the blame lands squarely on artificial intelligence.

Moonwell, a decentralized lending protocol, just watched $1.78 million vanish into the digital ether. The culprit? According to initial reports, a vulnerability linked directly to code generated by Anthropic's flagship AI model, Claude Opus 4.6.

When Smart Contracts Aren't So Smart

The exploit didn't need a sophisticated hacker—just a flaw in the logic. The AI-generated code apparently contained a critical oversight, creating a backdoor that allowed funds to be drained without proper authorization. It bypassed standard security checks, turning a tool meant to accelerate development into a liability.

The AI Accountability Question

This incident cuts to the core of a growing debate in Web3: who's responsible when AI writes buggy code? Teams lean on these models for speed and efficiency, but this breach shows the stark downside. It's not just a bug; it's a $1.78 million reminder that no algorithm yet replaces rigorous, human-led auditing.

A Costly Lesson in Automation Trust

The finance sector loves to tout 'efficiency'—until that efficiency automates a seven-figure loss. This exploit serves as a cynical jab at the industry's rush to adopt shiny new tools without fully vetting the risks. The promise of AI-driven development now carries a hefty price tag and a major credibility hit.

Moonwell's breach forces a reckoning. As protocols race to integrate AI, security can't become an afterthought. The market might forgive a hack, but it won't forget if the root cause becomes a trend. For now, the only thing mooning is the exploit's total—a sobering counter-narrative to crypto's bullish dreams.

Claude co-authored code set cbETH price at $1.12 instead of $2,200

The vulnerability appeared on February 15, just after Moonwell activated governance proposal MIP-X43, which integrated Chainlink’s Oracle Extractable Value (OEV) wrapper contracts across Base and Optimism markets.

As such, instead of calculating the cbETH price in USD by multiplying the cbETH/ETH exchange rate by the ETH/USD price feed, the deployed code obtained only the cbETH/ETH exchange rate and treated that ratio as if it were already denominated in dollars.

With cbETH trading at lower prices because of Moonwell’s oracle, liquidators could repay around $1 worth of debt and get collateral worth thousands in return.

Moonwell’s risk manager was able to reduce the cbETH borrow cap to 0.01 within hours of the vulnerability, effectively freezing new borrowing activity and containing further damage.

However, liquidations had already been processed, so users were left with catastrophic losses.

The protocol also estimated total losses at $1.78 million, mostly affecting cbETH, WETH, and USDC positions. Some borrowers nearly lost all their collateral as well, while others exploited the incorrect pricing to borrow even more money than they should have been allowed to, thus creating more debt within the protocol.

Bithumb suffered similar value assignment error just days earlier

The Moonwell incident is very similar to an error made at the South Korean exchange Bithumb just days earlier, on February 6, where a wrong-unit assignment created tens of billions of dollars in ghost value.

Apparently, a Bithumb staff member entered “BTC” instead of “KRW” while distributing rewards for a Random Box promotion, thus rewarding users in bitcoin instead of Korean won.

The project lost approximately 620,000 Bitcoin worth over $40 billion (nearly 3% of Bitcoin’s entire global supply).

Vibe coding debate intensifies

The Moonwell incident has re-sparked the debate over vibe coding. Advocates argue that AI makes coding more accessible, while critics warn that its code may contain vulnerabilities that human reviews WOULD most likely miss.

Smart contract auditor Pashov emphasized that “behind the AI is a person who checks the finished work, and possibly an auditor. For this reason, blaming the neural network alone is incorrect, although the incident ‘raises concerns’ about vibe coding.”

Anthropic’s Claude Opus 4.6 blamed for Moonwell's $1.78M loss in smart contract exploit.

Source: @pashov via X/Twitter.

Another blockchain security firm, SlowMist, shared its concerns about “oracle formula vulnerability” and the breakdown of human oversight that allowed the flawed code to reach production.

A study published just weeks before the Moonwell incident identified 69 vulnerabilities across 15 applications created using popular AI coding tools, including Cursor, Claude Code, Codes etc.

Even more interesting is that Anthropic’s own research from December 2025 revealed that Claude Opus 4.5 could exploit smart contract vulnerabilities worth $4.6 million by itself (in simulated environment). The research also established that premier AI models can now “independently identify vulnerabilities, create working exploit chains, and extract value with minimal human oversight.”

Nonetheless, Moonwell clarified that “no other markets on Base or OP Mainnet were affected. The issue is isolated to the cbETH CORE Market on Base.”

The protocol also noted that this was not its first oracle incident, recalling a misreporting incident in November 2025.

Don’t just read crypto news. Understand it. Subscribe to our newsletter. It's free.

|Square

Get the BTCC app to start your crypto journey

Get started today Scan to join our 100M+ users

All articles reposted on this platform are sourced from public networks and are intended solely for the purpose of disseminating industry information. They do not represent any official stance of BTCC. All intellectual property rights belong to their original authors. If you believe any content infringes upon your rights or is suspected of copyright violation, please contact us at [email protected]. We will address the matter promptly and in accordance with applicable laws.BTCC makes no explicit or implied warranties regarding the accuracy, timeliness, or completeness of the republished information and assumes no direct or indirect liability for any consequences arising from reliance on such content. All materials are provided for industry research reference only and shall not be construed as investment, legal, or business advice. BTCC bears no legal responsibility for any actions taken based on the content provided herein.