Slide 5 of 28
Part 1 — What Is It?Slide 5
Slide 5 · The Outcomes
What AG05 attacks and failures actually produce — real consequences from code that ran when it shouldn't have
💥
Irreversible data destruction
An agent executing DELETE, DROP TABLE, or rm -rf against production systems with no confirmation step. Database records, files, or entire schemas are gone before anyone realizes what happened. Without backups, the data is unrecoverable.
📡
Remote code execution on host systems
A code interpreter that escapes its sandbox — through a vulnerability in the interpreter, an OS-level call, or a container escape — gains execution access to the underlying host. From there, the attacker can move laterally to other systems on the same network.
🔓
Credential and secret exfiltration
Agent-generated code that reads environment variables, config files, or secret stores and sends their contents to an external endpoint. A coding agent with filesystem access and network access can exfiltrate API keys, database passwords, and private certificates in a single generated script.
🚪
Backdoor insertion in generated code
An agent manipulated by crafted input generates application code containing a hidden backdoor — a hardcoded credential, a reverse shell, a hidden API endpoint — which is then committed, deployed, and running in production before anyone reviews it.
🌊
Resource exhaustion and denial of service
Recursive code, infinite loops, or code that spawns unlimited subprocesses can consume all available CPU, memory, or disk space on a host — crashing services and making systems unavailable. An agent without resource limits can cause a self-inflicted denial of service.
⚙️
Unauthorized infrastructure changes
An infrastructure agent that generates and applies Terraform, Ansible, or Kubernetes manifests can modify cloud configurations, open firewall rules, change IAM policies, or provision expensive resources — instantly, at scale, without a human review step.
← Back Who triggers AG05 — and how? →