Researchers urge treating AI agents as untrusted systems, warning of crypto security risks

A new paper argues AI models should be handled like untrusted processes in an operating system, with least-privilege sandboxing and strict data separation to prevent attacks on crypto wallets and DeFi protocols.

Share

Add us on Google by Editorial Team May. 26, 2026

Your favorite AI assistant might be smart, but researchers now argue it should be treated with the same suspicion your computer treats a random downloaded program. A May 2026 paper published on arXiv makes the case that AI agents, especially those handling financial transactions, need to be architected as fundamentally untrusted components within larger systems.

The paper, titled “Agent Security is a Systems Problem” (arXiv:2605.18991), arrives at a moment when the crypto industry is betting heavily on autonomous AI agents to manage everything from DeFi trades to wallet operations. Circle CEO Jeremy Allaire has projected that billions of AI agents will independently conduct economic activities using stablecoins within the next three to five years.

The operating system analogy

Modern operating systems don’t trust individual processes. Every application runs in a sandbox with limited permissions, can only access files it’s been explicitly granted, and gets terminated if it tries to reach beyond its boundaries. The researchers want the same philosophy applied to AI agents.

Advertisement

The paper advocates for three specific measures. First, enforcing security invariants at the system level, meaning hard rules that can’t be overridden by the AI itself. Second, implementing least-privilege sandboxing, where agents only get access to the minimum resources needed for their specific task. Third, ensuring effective separation of instructions from data, which addresses one of the most dangerous attack vectors in AI systems today.

That last point matters more than it might sound. Prompt injection attacks work precisely because AI agents often can’t distinguish between legitimate instructions and malicious data that contains hidden commands. When an agent processes a transaction memo that secretly contains instructions to redirect funds, the lack of separation becomes a $500,000 problem.

The $500K wake-up call

That number isn’t hypothetical. An April 2026 incident resulted in exactly that amount being drained from a crypto wallet due to flaws in AI infrastructure and malicious tool calls. The attack exploited the kind of vulnerability the researchers are warning about: an AI agent with too much access, insufficient verification of the tools it was calling, and no system-level guardrails to catch the anomaly before funds left the wallet.

The autonomous nature of these agents compounds the risk. A human trader who gets a phishing email might pause and think. An AI agent that receives a carefully crafted prompt injection executes it at machine speed, potentially draining assets before any monitoring system can react.

Hardware and governance responses

Some companies are already moving in the direction the paper recommends. Ledger has outlined a 2026 security roadmap that includes hardware security initiatives specifically designed for AI agent environments. The logic is straightforward: if you can’t fully trust the software layer, anchor critical operations in hardware that provides cryptographic guarantees independent of the AI’s behavior.

The paper’s recommendation to treat this as a “systems problem” rather than a “model problem” is a meaningful distinction. It shifts responsibility from AI developers alone to the broader ecosystem of infrastructure providers, protocol designers, and platform operators.

What this means for investors

Watch for protocols that implement verifiable computation for AI agent actions, on-chain attestation of agent behavior, and mandatory least-privilege access controls. These features will likely become table stakes for institutional-grade AI agent platforms within the next 12 to 18 months.

Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.