TL;DR: AI agents can exploit financial logic flaws faster than they can defend them, with ClawSecure tying that gap to Moonwell and EVMBench. In agentic finance, intent checks, authority limits, and runtime containment matter before funds move.
Editorial analysis by NHI Mgmt Group, based on content published by ClawSecure: “When AI Writes the Code That Moves Your Money: Lessons from the Moonwell Exploit and OpenAI's EVMBench”.
By the numbers:
- The Moonwell exploit cost $1.78 million after a pricing formula valued cbETH at $1.12 instead of roughly $2,200.
- OpenAI's GPT-5.3-Codex achieved a 72.2% success rate in exploit mode but performed substantially worse at detection and patching.
Key questions
Q: Why do AI agents create more risk than traditional automation?
A: AI agents create more risk because they can interpret context, choose actions, and invoke tools autonomously.
Q: How do teams know whether agentic delivery controls are actually working?
A: Look for evidence that every important action is mediated, recorded, and bounded.
Q: What breaks when agentic systems can move money before humans review the decision?
A: The control breaks at the point where a wrong conclusion becomes an irreversible action.
Practitioner guidance
- Audit autonomous financial workflows for authority boundaries Map where AI or code can value assets, move funds, or trigger liquidations without a fresh human decision, then reduce those paths to task-scoped authority.
- Require intent checks before execution For pricing, trading, or liquidation logic, validate that the system's output matches the intended calculation and fails closed when context is incomplete.
- Separate exploit testing from patch testing Test whether your controls can detect abuse as well as they can repair defects, because a system that can exploit faster than it can defend needs tighter runtime restrictions.
Bottom line: The article shows that agentic systems can be better at exploiting financial logic flaws than defending against them.
Glossary terms: Agentic Finance, Intent Verification, Standing authority, Exploitability Asymmetry
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Agentic finance creates a verification gap, not just a coding gap. The Moonwell incident shows that code can be reviewed, audited, and still be unsafe when the computation it performs is wrong in context. That is the central governance failure mode in agentic systems that can move value: review assumes the code is the problem, while the real issue is whether the system is authorised to act on a wrong conclusion. Practitioners should treat contextual correctness as a control objective, not a nice-to-have.
A few things that frame the scale:
- 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What is the difference between safe agent delegation and unsafe standing authority?
A: Safe delegation is task-scoped, time-bounded, and checked before each high-risk action. Unsafe standing authority persists across steps or sessions, so the agent can keep acting after the original trust decision no longer applies. In practice, the difference is whether the system must earn each sensitive action or can continue indefinitely once access is granted.
👉 Read our full editorial: Agentic code can move money faster than it can be defended