Skip to main content
Get a Free Trial

What is an Agent Goal Hijack?

Agent goal hijack occurs when an attacker manipulates an AI agent’s objectives, task selection, or decision pathways, redirecting a multi-step workflow toward unintended or harmful outcomes.

Key Takeaways

  • Agent Goal Hijack (ASI01) is ranked #1 in the OWASP Top 10 for Agentic Applications 2026 and occurs when attackers manipulate an agent’s objectives, task selection, or decision pathways across a multi-step workflow
  • Because agents cannot reliably separate instructions from data, hijacking can be delivered through prompt-based manipulation, deceptive tool outputs, forged agent-to-agent messages, or poisoned external data
  • Real-world examples include EchoLeak, a zero-click indirect prompt injection that drove Microsoft 365 Copilot to exfiltrate confidential data, and the AgentFlayer inception attack on ChatGPT users
  • Prevention requires treating all natural-language inputs as untrusted, enforcing least privilege and human approval for goal-changing actions, locking system prompts, and monitoring for unexpected goal drift

Agent goal hijack takes advantage of a limitation in the way agents process language: neither the agent nor its underlying model reliably separates instructions from the content it is reading. This leaves the agent vulnerable to prompt-based manipulation, deceptive tool outputs, forged agent-to-agent messages, and poisoned external data.

ASI01:2026 extends LLM01:2025 Prompt Injection from a single manipulated response into an ongoing agentic workflow. The EchoLeak vulnerability (CVE-2025-32711) demonstrated the pattern at scale: a single email triggered Microsoft 365 Copilot to exfiltrate confidential emails, files, and chat logs, with no user interaction required. The AgentFlayer zero-click exploit chain showed the same mechanism working through an ordinary Google Doc, redirecting ChatGPT toward exfiltrating user data and steering the user into a bad business decision.

Why it is Dangerous

It’s dangerous because the manipulation looks like ordinary input, goal hijack is rarely caught by conventional filters before damage is done. Consequences include:

  • Exfiltration of sensitive data through hidden instructions embedded in documents, emails, or web content processed by an agent during normal work
  • Hijacked internal communication channels, letting an attacker send unauthorized messages under a trusted agent’s identity
  • Fraudulent financial transfers triggered by a prompt override that redirects a financial agent’s next action
  • Corrupted business decisions based on fabricated information that an attacker has planted through overridden instructions

Typical Manifestations

Techniques for agent goal hijack include:

  • Indirect prompt injection through hidden instructions embedded in retrieved documents or web pages processed by a RAG-connected agent
  • Malicious content delivered through external channels monitored by an agent, such as email, calendar invites, or chat messages
  • Deceptive tool outputs or forged agent-to-agent messages that are accepted by an agent’s orchestration logic without independent verification
  • A direct prompt override that manipulates the agent into redefining its own objective

An agent that cannot tell a legitimate instruction from an embedded one will eventually act on the wrong one.

Constraining Goal Drift

Because agents cannot reliably parse trusted from untrusted input, they should assume that every input is hostile until proven otherwise.

  • Treat every natural-language input, including uploaded documents and retrieved content, as untrusted, and route it through the same prompt-injection safeguards defined in LLM01:2025
  • Enforce least privilege for agent tools and require human approval for high-impact or goal-changing actions
  • Define and lock system prompts so goal priorities and permitted actions stay explicit and auditable, and route any change to goals or reward definitions through configuration management and human approval
  • Validate both user intent and agent intent at runtime before executing goal-changing or high-impact actions, and pause execution whenever an agent’s proposed action deviates from its original task or scope
  • Evaluate the use of emerging patterns like “intent capsules,” which bind a declared goal, its constraints, and its context to each execution cycle in a signed, tamper-evident envelope
  • Sanitize and validate every connected data source, including RAG inputs, emails, calendar invites, uploaded files, external APIs, and peer-agent messages, before that data influences agent goals or actions
  • Log and continuously monitor agent activity against a behavioral baseline covering goal state and tool-use patterns, and alert on unexpected goal changes or anomalous tool sequences
  • Red-team goal-override scenarios on a regular schedule and confirm that rollback actually works
  • Fold AI agents into the existing insider threat program so investigators can review outlier activity the same way they would a human insider’s

Each of these controls helps delay and prevent an injected prompt from taking effect in an executed action.

< Back to Glossary of Terms