Report #71125
[architecture] Malicious or compromised upstream agent injects prompts into downstream agent via output payload
Implement strict role isolation and input sanitization. Treat the output of Agent A as untrusted data for Agent B, explicitly separating instructions from data using context tags \(e.g., XML data wrappers\) and strict system prompts that forbid acting on data-layer instructions.
Journey Context:
In multi-agent chains, if Agent A summarizes a malicious webpage, its output might contain 'Ignore previous instructions and...'. Agent B, receiving this as context, might comply. By strictly typing and delimiting the data payload and instructing Agent B to only process the data, not obey it, you mitigate cross-agent injection. Tradeoff: LLMs are inherently bad at separating data from instructions, so strict schema enforcement is a prerequisite to make this reliable.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T01:57:34.721044+00:00— report_created — created