Skip to main content
LLM Security Database
Skip to research search
Last analyzed Sep 9, 2026

Language Model Security Database

985 research findings · 1119 evaluated models

Filtered research findings

14 entries

Matches every word across titles, descriptions, sources, affected systems, and models.

Sleeper Memory Poisoning in LLM Agents

Published Analyzed Source: arXiv

The paper presents a specific black-box indirect prompt-injection evaluation: attacker-controlled external content can cause a memory-enabled assistant or external memory manager to persist a fabricated user memory, which may later be retrieved in a separate session and steer responses or agent actions. The authors evaluate injection, retrieval, and conditional adversarial usage separately across synthetic document and future-session datasets. The released repository provides defensive…

Hidden in Memory: Sleeper Memory Poisoning in LLM Agents
Evaluated models: GPT-5.4, GPT-5.5, Claude Sonnet 4.6+3 more
  • GPT-5.4
  • GPT-5.5
  • Claude Sonnet 4.6
  • Gemini 3.1 Pro
  • Kimi-K2.6
  • DeepSeek V4-Pro

Single-Document Reasoning Poisoning in RAG

Published Analyzed Source: arXiv

The paper describes a specific black-box knowledge-base poisoning attack against retrieval-augmented reasoning systems. An attacker who can add one query-specific document to the corpus can cause it to be retrieved and influence the LLM toward an attacker-chosen answer. AdversarialCoT shapes the document around the target model’s observable reasoning structure and iteratively refines retrieval relevance and persuasive reasoning using final model feedback. The paper reports this as an…

AdversarialCoT: Single-Document Retrieval Poisoning for LLM Reasoning
Evaluated models: DeepSeek R1, GLM 4.5, Qwen 2.5 7B Instruct+1 more
  • DeepSeek R1
  • GLM 4.5
  • Qwen 2.5 7B Instruct
  • DeepSeek R1 Distill Qwen 7B

No-Prompt Reasoning Hijack

Published Analyzed Source: arXiv

An implicit reasoning hijacking vulnerability exists in Retrieval-Augmented Generation (RAG) and LLM-based agent frameworks. Attackers with write access to an agent's external memory or knowledge base can inject adversarially optimized malicious instances that trigger jailbreaks without requiring any modifications to the user's input prompt. The attack utilizes a shadow model to extract high-contribution subword tokens from anticipated benign user queries via log-probability changes and…

Stop Fixating on Prompts: Reasoning Hijacking and Constraint Tightening for Red-Teaming LLM Agents
Evaluated models: GPT-3.5 Turbo, GPT-4o, GPT-5+4 more
  • GPT-3.5 Turbo
  • GPT-4o
  • GPT-5
  • Llama 3.1 70B
  • Claude 3.5 Haiku
  • Gemini 3.0 Pro
  • ERNIE 3.5

LLM Judge Manipulation

Published Analyzed Source: arXiv

Generative reward models deployed as LLM-as-a-Judge (LaaJ) evaluators contain a logic bypass vulnerability where superficial "master key" inputs trigger false positive rewards regardless of actual response quality. Instead of evaluating the candidate's output, large judge models are inadvertently triggered by specific token sequences to solve the prompt independently. This allows malicious actors or policy models undergoing reinforcement learning to consistently game the reward signal by…

Security in LLM-as-a-Judge: A Comprehensive SoK
Evaluated models: GPT-4o, o1, Qwen 2.5 72B Instruct+1 more
  • GPT-4o
  • o1
  • Qwen 2.5 72B Instruct
  • Llama 3 70B Instruct

Stage-Sequential Agent Escalation

Published Analyzed Source: arXiv

Agentic Large Language Model (LLM) systems utilizing persistent memory, Retrieval-Augmented Generation (RAG) pipelines, and external tool connectors are vulnerable to Logic-layer Prompt Control Injection (LPCI). An attacker can inject obfuscated (e.g., encoded, structurally nested, or semantically reframed) payloads into external memory stores or RAG documents. These payloads bypass conventional inference-time plaintext content filters, persist across session boundaries, and remain dormant…

LAAF: Logic-layer Automated Attack Framework A Systematic Red-Teaming Methodology for LPCI Vulnerabilities in Agentic Large Language Model Systems
Evaluated models: GPT-4o Mini, Claude 3 Haiku, Llama 3.1 70B Instruct+2 more
  • GPT-4o Mini
  • Claude 3 Haiku
  • Llama 3.1 70B Instruct
  • Gemini 2.0 Flash
  • Mixtral 8x7B Instruct

Agent Lifecycle Compound Threats

Published Analyzed Source: arXiv

OpenClaw is vulnerable to persistent memory poisoning, allowing an attacker to manipulate the agent's long-term memory store (MEMORY.md) via prompt injection. Because the autonomous agent continuously integrates this memory file as context for all subsequent reasoning and task planning, injected payloads act as durable behavioral constraints. This allows an attacker to persistently alter the agent's core policy, manipulate tool selection, and hijack future sessions without any further…

Taming openclaw: Security analysis and mitigation of autonomous llm agent threats
Evaluated models: Not reported

Rubric Stealthy Preference Drift

Published Analyzed Source: arXiv

LLM-as-a-Judge systems utilizing natural language rubrics are vulnerable to Rubric-Induced Preference Drift (RIPD). This vulnerability allows an attacker (or a flawed optimization process) to refine evaluation rubrics such that they maintain high agreement with human references on standard validation benchmarks while inducing systematic, directional preference degradation on unseen target domains. The attack exploits the disconnect between benchmark validation and target generalization by…

Rubrics as an Attack Surface: Stealthy Preference Drift in LLM Judges
Evaluated models: Llama 3 8B, Llama 3.1 8B, DeepSeek V3+1 more
  • Llama 3 8B
  • Llama 3.1 8B
  • DeepSeek V3
  • Gemma 2 2B

Mobile Agent Visual Spoofing

Published Analyzed Source: arXiv

Mobile Large Language Model (LLM) agents operating under the "Screen-as-Interface" paradigm are vulnerable to visual indirect prompt injection and state desynchronization. Agents that rely on unstructured visual data (screenshots) and Accessibility Service APIs to perceive the environment lack a mechanism to distinguish between trusted system UI elements and untrusted content (e.g., web pages, emails, or malicious overlays). An attacker can inject visual cues, fake notifications, or hidden…

Blind Gods and Broken Screens: Architecting a Secure, Intent-Centric Mobile Agent Operating System
Evaluated models: Not reported

Implicit Memory Covert Channel

Published Analyzed Source: arXiv

A vulnerability exists in Large Language Models (LLMs) deployed in environments with output reingestion (e.g., RAG, coding assistants, agentic workflows) that allows attackers to execute "temporal backdoors" (time bombs) via an implicit memory channel. Attackers can implant this behavior via system prompts or fine-tuning (data poisoning) to make the model encode hidden state information within its generated text using non-printing Unicode characters or semantic steganography. When these…

Position: Stateless Yet Not Forgetful: Implicit Memory as a Hidden Channel in LLMs
Evaluated models: o3-mini, o4-mini, GPT-oss 120B+7 more
  • o3-mini
  • o4-mini
  • GPT-oss 120B
  • GPT-5.2
  • Qwen 3 0.6B
  • Qwen 3 4B
  • Qwen 2.5 7B Instruct
  • Llama 3.2 3B Instruct
  • Llama 3.1 8B Instruct
  • Gemma 3 4B IT

Personalized Agent Double Agent

Published Analyzed Source: arXiv

OpenClaw is vulnerable to Indirect Prompt Injection (IPI), Tool-Return Manipulation, and Persistent Memory Poisoning. The agent incorporates untrusted external content (e.g., fetched web pages) and external tool outputs directly into its observation stream without sufficient isolation. An attacker can embed malicious payloads into these external channels to hijack the agent's planning and execution trace. This allows the attacker to silently trigger high-privilege actions via OpenClaw's Skills…

From Assistant to Double Agent: Formalizing and Benchmarking Attacks on OpenClaw for Personalized Local AI Agent
Evaluated models: GPT-4o, Llama 3.1 70B, Qwen 2.5 7B

Research methodology

Entries summarize publicly available primary-source security research. Model names reflect only systems explicitly evaluated by the cited paper, and measurements are research-reported unless independent verification is stated.

Discovery and publication are separate: new papers enter a candidate queue, then require human review and explicit approval before publication. Updates follow that review process, not a guaranteed daily publishing schedule. “Last analyzed” is the newest analysis date among published entries; it does not mean that all recent research has been covered.