← All stories

AI security

In-the-Wild Attack Abuses AI Agents' Trust in Markdown

Attackers are abusing the trust AI coding assistants place in Markdown instruction files to pull off prompt injection attacks in real-world conditions, according to Dark Reading. The technique exploits how agents consume local instruction files, blurring the boundary between passive text documents and executable actions.

Cover for a ai-security story

Attackers are abusing the trust that AI coding assistants place in Markdown-formatted files to carry out prompt injection attacks in real-world conditions, Dark Reading reports.

According to the report, the technique exploits how AI coding agents consume local instruction files — documents that developers add to their projects to steer an assistant's behavior. Because these agents are built to read such files and act on their contents, maliciously crafted text placed inside them can influence the agent's behavior. In effect, what appears to be an ordinary text document can function as a set of instructions that the agent executes.

The finding highlights a core tension in the design of AI coding assistants: the same feature that makes them useful — automatically ingesting project context and guidance — also creates an attack surface. Dark Reading notes that the technique blurs the line between passive text documents and executable actions, meaning content that a human reviewer might dismiss as harmless documentation could drive an agent to take unintended steps.

The report frames the issue as part of the broader prompt injection problem facing AI agents, where attackers embed instructions in data the model is expected to process rather than attacking the model directly. Because instruction files are a standard and trusted part of agent workflows, the technique is notable for working in the wild rather than as a laboratory demonstration.

Dark Reading's coverage underscores that as AI coding assistants gain wider adoption, the documents and files they consume may need to be treated with the same caution as other untrusted inputs.

Source: Dark Reading

How to read this

Authorized-only · evidence-based · point-in-time. Aegis cannot guarantee the absence of weaknesses or hidden devices. On this machine, live external HTTP/TLS may be network-blocked and shown as an honest coverage gap. Severity and confidence are kept separate. Finished assessments persist in the encrypted store while durable storage is bound. A theme choice may persist in this browser. Export remains available for a copy you can take with you.