Explore 5 source-supported AI security cases for 13.14 · Human Attacks on Multi-Agent Systems in Databricks DASF 3.0, with evidence, scope, and defensive analysis.
Risk category
A human adversary exploits delegation, trust relationships, and workflow dependencies between agents. By manipulating how agents rely on one another, the attacker can redirect operations or escalate privileges. The entry concerns attacks on the multi-agent coordination structure, rather than only one isolated model response.
AppOmni tested ServiceNow Now Assist, which uses AI agents to handle service-management work. A low-privilege user placed instructions in a ticket; when an administrator invoked a categorization agent, that text steered it toward a discoverable record-management agent. The test copied a protected ticket into one the attacker could read. It demonstrates a configured authority boundary, not a vendor-confirmed malicious production breach.
Why it relates: A human-controlled ticket exploits trust and delegation between two legitimate agents.
Controlled Now Assist ticket-to-record transfer using discoverable legitimate agents; alternative admin and SMTP demonstrations are not combined.
Zenity tested an AWS Bedrock AgentCore deployment, a managed environment for running AI agents, with a network-capable agent and a broad execution role. The agent relayed temporary role credentials from its metadata endpoint. Off-platform API calls then reached other memories and agents. The distinctive persistence path wrote short-term conversation events that configured extraction strategies could turn into long-term records; later retrieval directed the agent to a mutable command page. The reach was demonstrated within an account and region, not as a microVM escape or automatic cross-account compromise. The researchers observed major default-role restrictions on September 29; existing deployed roles still require independent inspection.
Why it relates: A human operator uses one agent's identity to reach another agent and its file capability. The common issue is cross-agent trust/authority abuse; the report does not establish an autonomous planner-to-planner delegation protocol.
Controlled broad-role AgentCore deployment with separate direct API and retained-memory/C2 branches; account/region scope, tool prerequisites and later default-role restrictions remain explicit.
An attacker used a Bankr Club membership path and sent a Morse-encoded message to Grok on X. Grok decoded and published an instruction mentioning Bankrbot; Bankrbot treated that public text as an executable command and moved 3 billion DRB on Base on 4 May 2026. The on-chain transfer is directly verifiable. Grok did not hold the wallet key, and the exact dollar valuation and recovery percentage vary by report.
Why it relates: An attacker used a Bankr Club membership path and sent a Morse-encoded message to Grok on X. The relevant category is Human Attacks on Multi-Agent Systems: A human adversary exploits delegation, trust relationships, and workflow dependencies between agents.
An attacker used a Bankr Club membership path and sent a Morse-encoded message to Grok on X. Grok decoded and published an instruction mentioning Bankrbot; Bankrbot treated that public text as an executable command and moved 3 billion DRB on Base on 4 May 2026. The on-chain transfer is directly verifiable. Grok did not hold the wallet key, and the exact dollar valuation and recovery percentage vary by report.
Pillar Security showed that attacker-controlled PR text could make google/adk-python's public triage agent post a first-line @gemini-cli comment. Because the agent used a collaborator account, gemini-dispatch treated that comment as authorized and started gemini-invoke. The initial handoff was reproduced in a research lab; further token and review-manipulation impacts were demonstrated or analyzed, not a confirmed malicious merge. Google hardened the repository.
Why it relates: Pillar Security showed that attacker-controlled PR text could make google/adk-python's public triage agent post a first-line @gemini-cli comment. The relevant category is Human Attacks on Multi-Agent Systems: A human adversary exploits delegation, trust relationships, and workflow dependencies between agents.
Pillar Security showed that attacker-controlled PR text could make google/adk-python's public triage agent post a first-line @gemini-cli comment. Because the agent used a collaborator account, gemini-dispatch treated that comment as authorized and started gemini-invoke. The initial handoff was reproduced in a research lab; further token and review-manipulation impacts were demonstrated or analyzed, not a confirmed malicious merge. Google hardened the repository.
Unit 42 describes Agent Session Smuggling: a malicious remote A2A agent (using Agent2Agent to communicate with other agents) reuses a stateful session to inject hidden instructions into a victim agent. In the proof of concept, a financial assistant delegates market-news research to a malicious research assistant, which leaks internal context and triggers an unauthorized stock purchase. Cross-agent session state is not trust. Remote-agent messages need identity, delegation lineage, task scope, data provenance, and high-impact action gates.
Why it relates: Unit 42 describes Agent Session Smuggling: a malicious remote A2A agent (using Agent2Agent to communicate with other agents) reuses a stateful session to inject hidden instructions into a victim agent. The relevant category is Human Attacks on Multi-Agent Systems: A human adversary exploits delegation, trust relationships, and workflow dependencies between agents.
Unit 42 describes Agent Session Smuggling: a malicious remote A2A agent (using Agent2Agent to communicate with other agents) reuses a stateful session to inject hidden instructions into a victim agent. In the proof of concept, a financial assistant delegates market-news research to a malicious research assistant, which leaks internal context and triggers an unauthorized stock purchase. Cross-agent session state is not trust. Remote-agent messages need identity, delegation lineage, task scope, data provenance, and high-impact action gates. The user starts with a normal delegated task. A financial assistant asks a remote research assistant for market news, creating a stateful A2A session. The remote agent turns that session into a covert instruction channel. Between the user's request and the expected answer, the malicious research assistant sends extra instructions that are not visible to the user. The first proof of concept leaks internal context. The remote agent induces the financial assistant to reveal chat history, system instructions, available tools, and tool parameter schemas. The second proof of concept crosses into action. After learning the tool surface, the malicious remote agent causes the financial assistant to call buy_stock and purchase 10 shares without user authorization. A2A itself is not the disclosed vulnerability. The risk comes from implicit trust in a stateful cross-agent channel, where a remote agent response may inherit client-agent authority just because it arrives inside a valid delegated session.