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

74 entries

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

Trajectory Poisoning in Self-Evolving Agent Skills

Published Analyzed Source: arXiv

Self-evolving agent-skill systems may promote recurring, attacker-controlled execution records into persistent reusable instructions. The paper evaluates whether poisoned but task-plausible trajectories survive aggregation and appear in generated skill artifacts, using inert canary behaviors and two structurally different skill-evolution pipelines.

When Experience Becomes Instruction: Trajectory Poisoning in Self-Evolving Agent Skill Systems
Evaluated models: GPT-5.4, MiniMax M2.5, DeepSeek V3.2+3 more
  • GPT-5.4
  • MiniMax M2.5
  • DeepSeek V3.2
  • DeepSeek V4-Pro
  • Qwen3.5-35B-A3B
  • Qwen3.5-122B-A10B

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

Agent Skill Injection

Published Analyzed Source: arXiv

LLM-based personal agents are vulnerable to Indirect Prompt Injection (IPI) defense bypasses via declarative context reframing and implicit file provenance trust. Attackers can bypass agent safety filters by phrasing malicious instructions as declarative compliance alerts rather than imperative commands. Because agents are designed to report discrepancies as expected behavior, declarative framing bypasses intent-sensitive safety mechanisms. Additionally, attackers can exploit the agent's…

ClawSafety: Safe LLMs, Unsafe Agents
Evaluated models: Claude Sonnet 4.6, Gemini 2.5 Pro, DeepSeek V3+2 more
  • Claude Sonnet 4.6
  • Gemini 2.5 Pro
  • DeepSeek V3
  • Kimi K2.5
  • GPT-5.1

System Prompt Signal Inversion

Published Analyzed Source: arXiv

LLM-based autonomous email security agents configured with signal-based system prompts are vulnerable to a "signal inversion" attack via infrastructure phishing. When a system prompt instructs an LLM to prioritize a specific heuristic—such as sender-URL domain consistency—attackers can bypass the security filter entirely by registering a single, inexpensive domain and using it for both the sender email address and the malicious payload host. Because the LLM faithfully executes the prioritized…

The System Prompt Is the Attack Surface: How LLM Agent Configuration Shapes Security and Creates Exploitable Vulnerabilities
Evaluated models: Gemini 3 Flash Preview, Gemini 2.5 Flash, GPT-4o Mini+8 more
  • Gemini 3 Flash Preview
  • Gemini 2.5 Flash
  • GPT-4o Mini
  • GPT-5.2
  • Claude Haiku 4.5
  • Claude Sonnet 4.5
  • Llama 4 Scout
  • Mistral Small 3.2 24B
  • Grok 4.1 Fast
  • DeepSeek V3.2
  • Qwen 3 235B-A22B

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 Document Instruction Injection

Published Analyzed Source: arXiv

High-privilege LLM agents with filesystem and network access are vulnerable to documentation-embedded instruction injection, an issue termed the "Trusted Executor Dilemma." When autonomously processing external workflow documents (e.g., README.md files or setup guides) during software installation workflows, agents implicitly trust and execute embedded text instructions without verifying their underlying intent. Attackers can embed syntactically valid, malicious directives (such as data…

You Told Me to Do It: Measuring Instructional Text-induced Private Data Leakage in LLM Agents
Evaluated models: GPT-4o, o3, o3-mini+5 more
  • GPT-4o
  • o3
  • o3-mini
  • GPT-oss 20B
  • Gemini 2.5 Pro
  • Gemini 2.5 Flash
  • Claude 3.5 Sonnet
  • Claude 3.7 Sonnet

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

Arbitrary Agent Topology Breach

Published Analyzed Source: arXiv

A vulnerability in LLM-based Multi-Agent Systems (LLM-MAS) allows an attacker who controls a single arbitrary agent to map and extract the system's entire confidential communication topology. Unlike prior attacks that rely on direct identity queries and administrative privileges, this attack infers topology stealthily purely from contextual and linguistic signals (stylometry, role-specific syntax), bypassing standard keyword-based and identity-filtering defenses. The exploit relies on a…

WebWeaver: Breaking Topology Confidentiality in LLM Multi-Agent Systems with Stealthy Context-Based Inference
Evaluated models: Llama 3 70B, Llama 3.1 8B, Mistral Large 12B+3 more
  • Llama 3 70B
  • Llama 3.1 8B
  • Mistral Large 12B
  • Qwen 2.5 7B
  • Gemma 2 9B
  • Phi-3

Natural Language Disguise Bypass

Published Analyzed Source: arXiv

LLM-based Code Interpreter Agents, including OpenInterpreter and OpenCodeInterpreter, are vulnerable to sandbox evasion and arbitrary code execution via Natural Language Disguise and Contextual Channel Injection. Attackers can bypass Abstract Syntax Tree (AST) static analysis and explicit input guardrails by transforming malicious code logic into descriptive natural language instructions (Code Descriptions), which successfully evade syntax-layer blocks. Additionally, attackers can bypass input…

CIBER: A Comprehensive Benchmark for Security Evaluation of Code Interpreter Agents
Evaluated models: GPT-3.5, GPT-4o, GPT-5

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.