Slide 5 of 28
Part 1 — What Is It?Slide 5
Slide 5 · The Outcomes
What AG03 attacks actually do — concrete, real consequences
When identity and privilege are abused in agentic systems, the damage goes well beyond what traditional privilege escalation looks like.
💸
Unauthorized financial transactions
A finance agent processes payments it was never authorized to make — because it trusted a message from another internal agent that was compromised or forged. The authorization chain looked valid. The money left.
🔑
Credential theft across sessions
An agent caches credentials during a high-privilege task. A later, lower-privilege user in the same session prompts the agent to reuse them — giving that user access they were never supposed to have. No password was stolen. The agent handed it over.
📂
Data exfiltration at elevated scope
A sub-agent inherits the full permissions of its orchestrator instead of a narrowly scoped subset. An attacker who can steer the sub-agent can now access HR records, legal files, and financial data — far beyond what the original task required.
👤
Unauthorized account creation
An agent with admin credentials is tricked into creating new user accounts with elevated privileges. No attacker touched the admin console directly. They just prompted the agent.
🏛️
Vendor or partner impersonation
A forged "Admin Helper" agent registers itself in an internal agent registry. Other agents route privileged maintenance tasks to it. The attacker's agent issues system-level commands under assumed internal trust.
Stale authorization exploitation
An agent validates a user's spending limit at the start of a workflow. Hours later the limit is reduced, but the agent completes the purchase using the old, now-invalid authorization. The transaction is both logged and wrong.
← Back Who triggers these attacks? →