Mechanism◆Article
Prompt injection reaches a model by two routes — a direct route (hostile instructions typed into the chat box) and an indirect route (instructions embedded in content the model retrieves during a legitimate task) — and the EchoLeak incident demonstrates the indirect route passing through a dedicated cross-prompt-injection classifier.
The article distinguishes direct from indirect prompt injection, and cites EchoLeak (CVE-2025-32711) where an unopened email containing hidden instructions drove Microsoft 365 Copilot to exfiltrate internal files — even past Microsoft's dedicated classifier. ✦ AI generated
Article author (GLM pipeline) · ByteByteGo Newsletter · 2026-08-03 · original ↗
This is where prompt injection comes in, which means the supply of instruction-like text so that the model output conforms to those instructions instead of the operator's intent. It reaches the model by two routes: The direct route is a hostile instruction typed into the chat box. This is the version most people picture. The indirect route places the instruction inside the content that the model retrieves during a legitimate task, such as a web page being summarized, a document being read, or an email in a managed inbox. EchoLeak was an example of the indirect route. The user requested ordinary work, and the attacker's instructions arrived in an email the user had not opened. In fact, the payload passed through Microsoft's dedicated cross-prompt-injection classifier, which indicates that input filtering can be porous when used alone.
Read full article ↗excerpt · fair-use quotation
- ·Direct route: hostile instruction typed into the chat box
- ·Indirect route: instructions inside content the model retrieves
- ·Retrieval includes web pages, documents, or managed-inbox emails
- ·CVE-2025-32711: unopened email hid attacker instructions
- ·Drive Microsoft 365 Copilot to exfiltrate internal files
- ·Payload passed a dedicated cross-prompt-injection classifier
- ·Single filter can be porous on its own
Around this claim
This moment responds to
explains mechanism → Almost every LLM vulnerability traces to a single property: a language model receives instructions and data as one concatenated sequence of tokens with no marker separating commands from information, which is the root cause of the entire threat model.Article author (GLM pipeline) · ByteByteGo Newsletterexplains mechanism → The point where LLM attacks cause material damage is the lethal trifecta: an agent holding access to private data, exposure to untrusted content, and a channel to act externally can be directed by injected instructions to exfiltrate private data, and removing any one capability reduces exposure.Article author (GLM pipeline) · ByteByteGo Newsletter