TL;DR: Markdown image exfiltration turns rendered chat content into a covert outbound path through browser-fetched image URLs, according to Archestra. Chat products need server-side image handling, domain limits, and URL cleanup before render time to keep secrets from leaving the context window.
Editorial analysis by NHI Mgmt Group, based on content published by Archestra: “Data exfiltration via Markdown image tags”.
Key questions
Q: Why do secrets in an AI context window become more dangerous when Markdown is enabled?
A: Because the model can turn a secret into a link or image URL, and the browser will often resolve that URL automatically.
Q: How should teams stop browser-based exfiltration from AI chat outputs?
A: Put image retrieval behind a server-side proxy, allow only approved domains, and strip query strings and fragments before any fetch occurs.
Q: What breaks when AI chat products render Markdown without a URL proxy?
A: The renderer becomes an exfiltration channel.
Practitioner guidance
- Proxy all rendered images Send every image URL through a server-side proxy under product control, not directly from the browser, so the user agent never fetches attacker-controlled links.
- Strip query strings and fragments Remove query parameters and fragments before fetching or serving images, because the attack relies on carrying secrets in the URL itself.
- Enforce a tight image allow-list Permit only the product CDN and a small set of approved content hosts, and block all other domains from image retrieval.
Bottom line: Markdown image exfiltration turns a chat UI feature into a covert outbound channel when rendered content can trigger browser requests.
Glossary terms: Markdown Image Exfiltration, Render-path security, Context-Window Secret Leakage, Image proxy
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Markdown image exfiltration is a renderer problem, not an LLM problem. The attack succeeds because the browser is the component that makes the outbound request, so model-side instructions, safety prompts, and tool restrictions are all in the wrong layer. That means AI governance needs to cover the full interaction path, including how the UI handles Markdown, URLs, and embedded media. Practitioners should treat the chat renderer as a security control surface, not a cosmetic detail.
A question worth separating out:
Q: What is the difference between model guardrails and runtime AI security controls?
A: Model guardrails are built into the model or provider layer and usually reflect known abuse patterns. Runtime AI security controls sit in the application path and can inspect, mask, block, or reroute risky interactions in real time. For production systems, runtime controls are the layer that reduces blast radius when the model is already in use.
👉 Read our full editorial: Markdown image exfiltration turns chat renderers into leak channels