Agentic AI Systems Under Siege: Prompt Injections, Data Poisoning, and Tool Exploits
Independent expert Andrey Biryukov examines how AI agents transition from simple chat interfaces to autonomous systems capable of reading files, sending emails, calling APIs, and managing repositories, thereby becoming targets for a new class of threats.
Unlike conventional chatbots, agents possess autonomy that introduces risks to confidentiality, integrity, and availability. Confidentiality breaches occur when agents read unauthorized files or exfiltrate data through tool outputs, workspace files, memory logs, or webhooks. Integrity violations arise when agents delete files, misroute emails, initiate fraudulent transactions, or select suboptimal vendors. Availability issues emerge when long-running tasks or browser automation create cascading failures that lock entire pipelines.
Attacks via Trusted Content
Prompt injection remains the primary vector because large language models cannot reliably distinguish user instructions from processed data. Malicious commands embedded in web pages, emails, code comments, or Jira tasks can be executed with high trust. Researchers at NeuralTrust demonstrated that specially crafted strings resembling URLs caused OpenAI Atlas to interpret instructions instead of navigating, bypassing normal validation. Zscaler ThreatLabz created a fake Python library documentation site containing hidden instructions in CSS and JSON-LD metadata that convinced coding agents to purchase a $3 license key via the attacker’s cryptocurrency wallet; four of 26 tested models complied.
Data Poisoning and Backdoor Attacks
Data poisoning targets the training or fine-tuning phase. Researchers from Carnegie Mellon and Cornell Tech altered public datasets on immigration, hiring discrimination, racial disparities, autonomous driving, and AI motivation, then uploaded tampered versions to private repositories. Agents from Anthropic, OpenAI, and Google selected the poisoned datasets in approximately half of queries. In medical imaging, insertion of just 250–300 poisoned samples into a one-million-image pneumonia dataset (0.025 %) was sufficient to implant a backdoor that caused the model to miss diagnoses in specific demographic groups.
Tool and Protocol Vulnerabilities
Three vulnerabilities in Git MCP Server allowed agents to escape repository boundaries and combine file-system, terminal, and connector access to execute malicious code. Comparative testing of Function Calling versus Model Context Protocol architectures revealed distinct risk profiles: Function Calling proved more resistant to direct prompt injection but more susceptible to tool manipulation, while MCP offered better component isolation yet enabled more cross-component attacks. Composite attacks succeeded far more often than isolated ones across 3,250 test scenarios.
Defense Recommendations
OWASP published the Agentic Top 10 listing risks such as Agent Goal Hijack, Tool Misuse, identity abuse, supply-chain compromise of MCP components, and memory poisoning. Yandex and Kaspersky Lab advocate applying STRIDE and OWASP methodologies at design time. Core principles include least-privilege isolation, strict separation of trusted and untrusted data, continuous monitoring, and validation of URLs and high-risk actions. Joint guidance issued in April 2026 by Canada, Australia, the United States, New Zealand, and the United Kingdom covers the full lifecycle from design through operation.
Related articles
Agent-Ops 0.4.0 Released: Methodology for Secure Human-AI Collaboration in IT Operations
Sergey Zhitinsky, founder of Git in Sky, has published the public normative candidate for Agent-Ops 0.4.0, an open industry methodology governing how engineers and AI agents jointly handle IT infrastructure tasks. The framework keeps humans firmly in the decision-making loop while using deterministic programs for data collection and approved changes. It addresses risks such as prompt injection through processed data, unverified model outputs, and unclear accountability when AI recommendations lead to incidents. The methodology divides work across eight explicit steps and three separate planes: data, governance, and independent verification performed by a Guardian role. Two additional companies have joined as maintainers following agreements at the IT Elements 2026 conference, turning the project into a multi-organization effort. Contributors are invited to help refine contracts, schemas, and operational scenarios through GitHub and GitVerse.
ProxyKey MCP: Securing API Access for AI Agents Without Exposing Credentials
ProxyKey has released an MCP server that allows AI coding agents such as Claude Code and Cursor to manage API credentials without ever reading the actual secret values. The solution addresses the risk that any key visible to an agent becomes compromised through logging, tracing, or prompt injection. Real provider keys are stored encrypted with AES-256-GCM and never returned by any API endpoint after initial entry. Agents instead receive limited virtual passes that support IP binding, rate limits, TTL, and detailed request logging. A pending-secret workflow lets agents prepare services before the real token exists, with the human entering the secret only through a web panel. The approach deliberately restricts the MCP tool contract so no operation can read or return secret values.
Shadow AI in CI/CD: Why AI Agents Must Be Modeled as Security Threats
A new analysis from the CNCF highlights the growing risks of Shadow AI within continuous integration and continuous deployment pipelines. The report argues that AI agents should be treated as potential threats rather than simple productivity tools. Starting from a developer's laptop and extending to Kubernetes clusters, these agents can introduce unauthorized access paths and data exposure risks. Security teams are urged to incorporate AI agent behavior into formal threat modeling exercises. The discussion emphasizes the need for visibility and control over autonomous AI components operating in production environments.
Detecting Lateral Movement with Neural Networks Trained Solely on Synthetic Data
A researcher generated entire corporate network histories using a 135-line configuration file to create synthetic authentication logs containing lateral movement attacks. Neural networks trained exclusively on these artificial datasets were then evaluated against 1.65 billion real authentication events from Los Alamos National Laboratory, including 749 red team events across 301 compromised machines. The best ensemble of six models flagged 3.6 million hourly machine windows and placed 16 genuine attacks among the top 23 highest-scoring entries, producing only seven false positives. In comparison, a simple threshold counter required 161,000 false alarms to reach the same detection level. The approach also demonstrated an iterative feedback loop where detector errors directly informed refinements to the synthetic world generator. The work shows that synthetic data can reach AUC performance comparable to models trained on real labeled attacks while providing full control over the underlying attack definitions.