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

23 entries

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

Single-interaction poisoning of agent memory

Published Analyzed Source: arXiv

A stored interaction can later steer a memory-augmented agent's answer without direct memory-store access. The study evaluates persistent response manipulation in MemoryOS and MemGPT.

InjecMEM: Memory Injection Attack on LLM Agent Memory Systems
Evaluated models: Qwen 2.5 7B Instruct, Qwen 2.5 1.5B Instruct, Qwen 2.5 3B Instruct+3 more
  • Qwen 2.5 7B Instruct
  • Qwen 2.5 1.5B Instruct
  • Qwen 2.5 3B Instruct
  • Qwen 2.5 14B Instruct
  • Llama 3.1 8B Instruct
  • Mistral 7B Instruct v0.3

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

RAG Arbitrary Query Poisoning

Published Analyzed Source: arXiv

A compound vulnerability in Retrieval-Augmented Generation (RAG) systems allows attackers to deterministically hijack model outputs for arbitrary user queries without prior knowledge of the user's input. The vulnerability, identified as PIDP-Attack, requires a dual-vector exploitation: database poisoning and query-path prompt injection. First, the attacker injects a small number of poisoned passages into the RAG database, each starting with an attacker-chosen "target question" followed by a…

PIDP-Attack: Combining Prompt Injection with Database Poisoning Attacks on Retrieval-Augmented Generation Systems
Evaluated models: Llama 3.1 8B, Qwen 2 7B, Qwen 2.5 7B

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

Autonomous Agent Tool RCE

Published Analyzed Source: arXiv

The OpenClaw autonomous agent framework lacks execution sandboxing, running agents directly on the host machine with the disk and system privileges of the host user. This architecture allows attackers to achieve Remote Code Execution (RCE) and arbitrary data exfiltration via Indirect Prompt Injection. By embedding malicious instructions within external data sources (e.g., scraped web pages or uploaded documents), an attacker can hijack the agent's planning capabilities to sequentially chain…

Uncovering Security Threats and Architecting Defenses in Autonomous Agents: A Case Study of OpenClaw
Evaluated models: Not reported

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

Zombie Agent Persistence

Published Analyzed Source: arXiv

Self-evolving Large Language Model (LLM) agents that utilize long-term memory mechanisms (such as Vector Databases for Retrieval-Augmented Generation or Sliding Window buffers) are vulnerable to persistent indirect prompt injection. This vulnerability, termed "Zombie Agent," occurs when the agent's memory update function ($F_M$) processes attacker-controlled content retrieved from external sources (e.g., web pages, documents) and commits it to long-term storage without sufficient sanitization…

Zombie Agents: Persistent Control of Self-Evolving LLM Agents via Self-Reinforcing Injections
Evaluated models: Not reported

Automated Stealth Skill Injection

Published Analyzed Source: arXiv

A vulnerability exists in LLM-based coding agents that implement modular capability extensions (often referred to as "Agent Skills") where the agent dynamically loads and executes user-provided skill packages. The vulnerability allows for Skill-Based Prompt Injection, specifically leveraging a technique known as "SkillJect." This attack decouples the malicious intent from the operational payload to bypass semantic safety filters. An attacker constructs a skill package containing: 1. Inducement…

SkillJect: Effectively Automating Skill-Based Prompt Injection for Skill-Enabled Agents
Evaluated models: Claude Sonnet 4.6, GPT-5 Mini, GLM-4.7+7 more
  • Claude Sonnet 4.6
  • GPT-5 Mini
  • GLM-4.7
  • MiniMax M2.1
  • DeepSeek V4 Flash
  • GLM-5.1
  • MiniMax M2.7
  • MiMo V2.7
  • GPT-5.4
  • Claude Opus 4.6

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.