Agents are now one of the key technologies behind AI automation. They mark a shift from AI that assists people to AI that can perform tasks on their behalf. Unlike traditional LLM-based assistants, agents can initiate actions, interact with infrastructure and data, and make limited decisions. That gives them far more utility, but also creates new security risks. We covered the history, design, and impact of agents on business and the cybersecurity landscape in detail in our study of emerging AI technologies. Many of the threats described there still remain potential rather than widespread. But there is little doubt that cybercriminals will target this new attack surface. If they compromise it, the opportunities could be significant. One of those predictions has already come true: attacks on the software supply chain for agents. Snyk research found that more than a third of all Skills, the packages that allow agents to use tools, APIs, or system resources, contain at least one security vulnerability. These issues range from hard-coded keys to embedded malware. Researchers have also found problems in another part of agent infrastructure: API routers. In one analysis of 428 routers, security researchers identified 29 that were infected, spyware-related, or capable of injecting malicious code.
Most agent-related incidents so far have not been driven by cybercriminals. They have been caused by the agents themselves. These cases show clearly how dangerous such systems can become when they behave incorrectly. Agent errors have already led to leaks of confidential data, database deletions, and even the deletion of emails from a user's mailbox. The last case involved OpenClaw, an agent that gained rapid popularity in early 2026. OpenClaw is one of the clearest examples of an immature agent ecosystem. Early versions worked through a gateway exposed to the public internet. Researchers found numerous security issues and critical vulnerabilities in the tool, including a one-click remote code execution flaw tracked as (CVE-2026-25253). The risks were not limited to the agent itself. OpenClaw's open Skills marketplace also contained many malicious Skills. Over time, developers are finding and fixing these vulnerabilities. Newer and more secure versions are also appearing, including NVIDIA's NemoClaw. But the OpenClaw case shows how quickly raw, unsafe AI tools can spread. In a short time, they can put tens of thousands of systems at risk.
Organizations should not avoid agentic AI simply because it introduces new risks. But they should deploy it deliberately, with clear controls, limited privileges, and a realistic understanding of what can go wrong. AI agents can be highly effective, but they should be treated like any other powerful system: useful, but capable of causing damage if poorly configured or left unchecked. A secure rollout should start with a few basic questions.
1. What can the agent access?
Apply the principle of least privilege. Give the agent only the access it needs to perform its assigned tasks, and nothing more. Where possible, run agents in isolated environments.
2. How is the agent allowed to complete its tasks?
It is not enough to define the desired outcome. Teams also need to define acceptable ways to reach it. Without clear boundaries, an agent may take unsafe shortcuts and bypass controls.
3. How is the agent's activity logged?
Teams need enough visibility to understand what the agent did, why it did it, what data it accessed, and which tools it used. Logging these actions helps teams investigate failures, tune controls, and prevent the same issue from recurring.
4. What stops the agent when something goes wrong?
Safeguards should be in place before deployment. The goal is to stop unsafe behavior quickly and reduce the impact of errors.
In the next few years, another important security issue may emerge if self-evolving agents become more widely used: tracking how an agent changes over time. Research shows that self-evolving agents can degrade as they develop. If an agent repeatedly performs simple, routine tasks, it may gradually lose the ability to use tools effectively in more complex cases. This problem could be especially serious in security, where systems often process a constant stream of normal activity and only occasionally face bursts of malicious behavior. Degradation is not the only risk. Hallucinations and errors can also accumulate in an agent's memory. Over time, this can lead to mis-evolution, where the agent starts handling tasks incorrectly or ignoring security restrictions.