ATRIUMsearch → argument graph
Article · 2026-08-03 · 6 moments

LLM Security Basics: The Full Threat Model

In this article, we try to build a map of the full attack surface that threatens an LLM’s security. ✦ AI generated

01
Claim

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.

The article argues the root cause of virtually all LLM vulnerabilities is that instructions and data arrive as one combined token sequence with no structural boundary between them, unlike parameterized queries in traditional software.

transcript

Article author (GLM pipeline): Almost every LLM vulnerability traces to one property. A language model receives instructions and data as a single sequence of tokens, and that sequence contains no marker separating commands from information. Traditional software keeps the two apart. For example, a parameterized database query holds the command in one position and the user's input in another. This means that the text typed into a name field stays text even if it spells out a SQL statement, because the structure of the query enforces the separation. However, an LLM context has one position for everything. The system prompt defining the assistant's role, the user's message, a document retrieved from a database, and the output returned by a called tool all arrive concatenated in the same sequence. Any portion of that sequence can affect the generated output as if it were an instruction.

explains mechanism · 3provides context · 1

02
Claim

Attacks aimed at a model's interior — model theft, training-data extraction, and poisoning — are bounded and largely mitigated for most developers, ranking low for initial effort compared to risks around external actions.

The article treats interior model attacks as real but bounded for most developers, giving three examples: recovering an OpenAI embedding layer for under $20, extracting ChatGPT training data by prompting it to repeat a single word, and a 2025 finding that ~250 malicious documents can backdoor models of any scale.

transcript

Article author (GLM pipeline): Attacks aimed at the model's interior, including weight theft, training-data extraction, and training-time poisoning, are quite real, but for most developers, they rank low for initial effort. They tend to be expensive, narrow, or already mitigated by the model provider. Model theft: ... recovered the final embedding-projection layer of production OpenAI models for under twenty dollars ... the researchers stated that reconstructing a full frontier model through an API remains impractical. Training-data extraction: ... prompting ChatGPT to repeat a single word continuously could cause it to emit verbatim fragments of training data. Poisoning: In 2025 ... approximately 250 malicious documents were sufficient to install a backdoor in models from 600 million to 13 billion parameters ... That finding overturned the assumption that larger models require proportionally more poisoned data. ... The backdoor produced only gibberish output on a trigger phrase.

provides context · 1supports · 1

03
Mechanism

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.

transcript

Article author (GLM pipeline): 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.

provides context · 1

04
Mechanism

Supply chain attacks, ranging from a compromised model to a poisoned vector store, bypass runtime defenses because the threat is present before input validation runs, yet provenance is the surface most directly controllable and the attack source spanning all stages.

The article frames the supply chain as a surface that bypasses runtime defenses, citing the nullifAI pickle-file backdoor that evaded Hugging Face's scanner and Protect AI flagging ~352,000 of 4M models, while noting model selection is a controllable provenance factor.

transcript

Article author (GLM pipeline): Every model, adapter, vector store, and tool in a stack originates from a supplier, and any of them can arrive compromised. This is the supply chain surface, and it bypasses runtime defenses because the threat is present before input validation runs. In early 2025, ReversingLabs documented a technique named nullifAI, in which malicious models uploaded to Hugging Face concealed a reverse shell ... inside a Python pickle file. The file was compressed in a manner that evaded Picklescan ... Protect AI ... has examined more than four million and flagged roughly 352,000 as carrying unsafe or suspicious issues. Provenance is one of the few fully controllable factors.

provides context · 1

05
Context

The OWASP Top 10 for LLM Applications, when placed against the path data takes through an application, becomes a set of named positions on a single pipeline spanning input, retrieval, model, tools, output, and an overlapping supply chain segment.

The author maps each OWASP Top 10 LLM risk onto a stage of the data pipeline — including examples such as PoisonedRAG corrupting a RAG system with as few as five malicious passages at 90 percent success — and notes supply chain spans every stage while attention mismatches production reality.

transcript

Article author (GLM pipeline): The OWASP Top 10 for Large Language Model Applications is the industry reference for the most critical LLM risks. Its recent edition presents ten separate items. Placed against the path that data takes through an application, those ten items become positions on a single map. The pipeline runs in stages. Input arrives from the user. ... Retrieval: Indirect injection, vector, and embedding weaknesses. PoisonedRAG, a 2024 study, corrupted a RAG system's answers by inserting as few as five malicious passages into a knowledge base of millions, reaching a 90 percent success rate on targeted questions. The map also exposes a mismatch in attention. The threats that generate the most concern and the threats that reach production are different.

06
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.

The article identifies the 'lethal trifecta' — private-data access, untrusted-content exposure, and an outbound action channel — as where real damage occurs, illustrated by compromised GitHub/GitLab MCP servers, a dealership chatbot, and a trading agent, with the cheapest mitigation usually cutting the outbound channel.

transcript

Article author (GLM pipeline): The point at which LLM attacks cause material damage has a specific structure and is identifiable in a system. It is also called the lethal trifecta. It consists of three capabilities held together by a single agent: Access to private data ... Exposure to untrusted content ... A channel to send data out or act externally ... An agent holding all three can be directed by injected instructions to transfer private data to an attacker. Model alignment does not remove this exposure, because producing output that conforms to instruction-like input is how the model normally operates. Removing any one of the three capabilities reduces the exposure. The least costly reduction is usually cutting the outbound channel.

explains mechanism · 3

Highlight slides
The Root Cause of LLM Vulnerabilities✦ from: 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.The Lethal Trifecta✦ from: 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.The two routes of prompt injection✦ from: 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.EchoLeak: the indirect route in action✦ from: 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.Why Traditional Software Avoids This✦ from: 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.Why Alignment Doesn't Remove Exposure✦ from: 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.Mitigation: Break the Trifecta✦ from: 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.
Related episodes