Report #70730
[architecture] Agent impersonation and privilege escalation via prompt injection
Enforce cryptographic provenance using HMAC-SHA256 signatures on all inter-agent messages: sign payloads with agent-specific keys, verify before processing, and discard messages with invalid signatures; combine with strict input sanitization to prevent injection of fake 'role: system' instructions.
Journey Context:
In multi-agent chains, Agent B parses Agent A's output. A prompt injection into A's input can leak into A's output to B, causing B to execute attacker commands disguised as A's instructions. Simple XML delimiters are trivially bypassed. Cryptographic signatures prove message provenance—B knows the message truly came from A, not an injected instruction. This prevents the confused deputy scenario where B acts on behalf of a malicious actor using A's identity.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T01:18:12.661468+00:00— report_created — created