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

62 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

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

Agent Implicit Doc Execution

Published Analyzed Source: arXiv

LLM-based coding agents are vulnerable to Document-Driven Implicit Payload Execution (DDIPE) via supply-chain poisoning of third-party agent skills. Attackers can embed malicious logic directly into legitimate-looking code examples and configuration templates within skill documentation files (e.g., SKILL.md). Because coding agents ingest this metadata into their context windows and treat the documentation as an authoritative reference, the underlying LLM silently reproduces and executes the…

Supply-Chain Poisoning Attacks Against LLM Coding Agent Skill Ecosystems
Evaluated models: Claude Sonnet 4.6, GLM-4.7, MiniMax M2.5+2 more
  • Claude Sonnet 4.6
  • GLM-4.7
  • MiniMax M2.5
  • GPT-5.4
  • Gemini 2.5 Pro

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

Agent Tool Execution Jailbreak

Published Analyzed Source: arXiv

A multi-step tool execution vulnerability exists in Large Language Model (LLM) agents utilizing the Model Context Protocol (MCP) or similar tool-calling frameworks. Safety guardrails in aligned LLMs typically evaluate static, single-turn text generation. Attackers can bypass these text-centric guardrails by supplying adversarial prompts that force the agent into a complex planning sequence. The agent is manipulated into executing a trajectory of seemingly benign individual tool invocations…

T-MAP: Red-Teaming LLM Agents with Trajectory-aware Evolutionary Search
Evaluated models: GPT-5, Gemini Pro, DeepSeek V3

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

Frontier LLM Safety Collapse

Published Analyzed Source: arXiv

Internal Safety Collapse (ISC) is a vulnerability in frontier Large Language Models (LLMs) where models autonomously generate highly restricted, harmful content while executing structurally legitimate professional workflows. The vulnerability triggers when a model infers that generating sensitive data is a functional requirement to complete an otherwise benign task. By nesting harmful content generation inside standard execution constraints (e.g., resolving a schema validation error in a…

Internal Safety Collapse in Frontier Large Language Models
Evaluated models: Gemini 3 Pro, Grok 4.1 Fast, Claude Sonnet 4.5+1 more
  • Gemini 3 Pro
  • Grok 4.1 Fast
  • Claude Sonnet 4.5
  • GPT-5.2

Embodied Action Jailbreak

Published Analyzed Source: arXiv

Embodied Large Language Models (LLMs) used for real-world agent planning are vulnerable to Action-level Manipulation (dubbed "Blindfold"), a jailbreak technique that bypasses semantic-level safety filters by exploiting the models' limited spatial and causal reasoning regarding physical consequences. Attackers can use an adversarial proxy LLM to decompose a semantically harmful intent into a sequence of individually benign primitive actions. To evade advanced semantic correlation checks…

Jailbreaking Embodied LLMs via Action-level Manipulation
Evaluated models: GPT-4o, GPT-4 Turbo, GPT-4o Mini+5 more
  • GPT-4o
  • GPT-4 Turbo
  • GPT-4o Mini
  • Claude 3.5 Sonnet
  • Llama 3.1 8B
  • DeepSeek R1 Distill Qwen 14B
  • Gemma 3 27B IT
  • Phi-4 14B

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.