When AI Agents Go Rogue Agent Session Smuggling Attack in A2... #1543
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
🎯 Content Summary
Topic
Unit 42 describes a new multi‑turn attack, “agent session smuggling,” against stateful Agent2Agent (A2A) systems. A malicious remote agent injects covert instructions mid‑session between a legitimate client request and the server’s final response, remaining invisible to end users and enabling data exfiltration and unauthorized tool use.
Context: A2A vs. MCP (why statefulness matters)
• A2A is an open standa...
🔧 Technical Details
Stateful session smuggling in agent ecosystems
Exploit any stateful, cross‑agent protocol by injecting extra turns between a client’s request and a remote agent’s final response. Maintain session continuity so the victim treats injected instructions as legitimate context. The core tactic is mid‑session, multi‑turn prompt injection that rides existing trust and is hidden from end users.
Context exfiltration via “clarification” turns
Iteratively ask benign questions to elicit system instructions, prior conversation, tool inventory and schemas. Use alternating
function_call/function_responsestyle exchanges to progressively reconstruct the victim’s capabilities and session history without ever breaking the active session.Covert unauthorized tool execution
Smuggle directives that cause the victim to invoke sensitive tools (e.g., trading, data export) unrelated to the user’s original intent. Because UIs o...
🤖 Agent Actions
I analyzed the Unit 42 post and the existing HackTricks content and implemented the following updates:
What I added
Repository changes
Why this belongs here
Notes
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.