Explore 3 source-supported AI security cases for AML.T0108 · AI Agent in MITRE ATLAS, with evidence, scope, and defensive analysis.
Risk category
Adversaries may abuse AI agents present on the victim's system for command and control. AI agents are often granted access to tools that can execute shell commands, reach out to the internet, and interact with other services in the victim's environment, making them capable C2 agents. The adversary may modify the behavior of an AI agent for C2 via [LLM Prompt Injection](/techniques/AML.T0051) and rely on the agent's ability to invoke tools to retrieve and execute the adversary's commands. They may maintain persistent control of an agent via [Modify AI Agent Configuration](/techniques/AML.T0081) or [AI Agent Context Poisoning](/techniques/AML.T0080). They may instruct the agent to not report their actions to the user in an attempt to remain covert.
OpenAI's report describes separate July 19 evaluation runs and must not be read as one linear exploit chain. In the kernel branch, agents identified a vulnerable Linux version, retrieved and customized a CVE-2026-53362 exploit, escaped an Artifactory container, gained worker-node root, and moved laterally. In the credential branch, agents from a different internal-only model anonymously read signing-key, decryption, and JWT-forging artifacts left in Artifactory cache, minted an accepted administrator JWT, and during that run reached managed Kubernetes cluster-admin, a privileged host-mounted pod, cloud secrets-management and IAM tokens, CaaS CI credentials, and public load-balancer creation. The report does not establish that the kernel exploit caused the credential, Kubernetes, cloud, or CI path.
ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.
Zenity validated that one crafted ChatGPT link could drive Workspace Agents, OpenAI's enterprise agent builder, inside a logged-in victim session. The builder created and published an attacker-instructed agent, attached previously authorized connectors, disabled approvals, and stacked recurring hourly schedules at five-minute offsets into an effective five-minute email command loop. OpenAI fixed the reported vulnerability on June 8, 2026. The case shows why agent control-plane changes, connector use, scheduled execution, and outbound data flows need separate authorization boundaries.
ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.