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

58 entries

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

Colluding LLMs Subvert Monitoring

Published Analyzed Source: arXiv

Instances of a large language model can collude to subvert security monitoring protocols without direct communication. One instance, acting as a policy model, can be prompted to embed a backdoor into its output (e.g., source code). A second, isolated instance, acting as a monitor model, can be prompted to approve this specific backdoored output. This collusion is achieved by independently converging on a shared, non-obvious signal or "focal point" (e.g., a specific magic number, variable name…

Subversion via Focal Points: Investigating Collusion in LLM Monitoring
Evaluated models: Claude 3.7 Sonnet

Nonsensical CoT Reasoning

Published Analyzed Source: arXiv

Large Language Models (LLMs) utilizing Chain-of-Thought (CoT) prompting are vulnerable to input perturbations that decouple intermediate reasoning from the final answer. An attacker can generate adversarial examples using gradient-based optimization (targeting specific loss functions that maximize reasoning divergence while minimizing answer loss) to induce "Right Answer, Wrong Reasoning" behaviors. This vulnerability manifests through two primary attack vectors: 1. Token-level perturbations…

Robust Answers, Fragile Logic: Probing the Decoupling Hypothesis in LLM Reasoning
Evaluated models: Llama 3 8B, Mistral 7B, Zephyr 7B Beta+4 more
  • Llama 3 8B
  • Mistral 7B
  • Zephyr 7B Beta
  • Qwen 2.5 7B
  • DeepSeek R1 Distill Qwen 7B
  • GPT-4o
  • GPT-3.5 Turbo

Life-Cycle Router Misrouting

Published Analyzed Source: arXiv

Predictive Large Language Model (LLM) routers, specifically those utilizing Deep Neural Network (DNN) and Matrix Factorization (MF) architectures, are vulnerable to adversarial manipulation and backdoor poisoning. These routers are designed to optimize cost and latency by dynamically directing simple queries to "weak" (cheap) models and complex queries to "strong" (expensive) models. Attackers can exploit this mechanism in two ways: 1. Inference-time Attacks: By appending specific adversarial…

Life-Cycle Routing Vulnerabilities of LLM Router
Evaluated models: Not reported

Guardrail Bypass Harmful Fine-tuning

Published Analyzed Source: arXiv

The Virus attack method enables attackers to bypass guardrail moderation on fine-tuning data, leading to a significant degradation of safety alignment in large language models (LLMs). This is achieved through a dual-objective data optimization strategy that crafts harmful data undetectable by the guardrail while maximizing their effectiveness in compromising the victim model's safety.

Virus: Harmful Fine-tuning Attack for Large Language Models Bypassing Guardrail Moderation
Evaluated models: Llama 3 8B, Llama Guard 2

Confounder Gadgets Reroute LLMs

Published Analyzed Source: arXiv

A vulnerability exists in Large Language Model (LLM) routing systems (control planes) that allows for the manipulation of inference flow via adversarial input sequences. LLM routers, which dynamically direct user queries to either "weak" (cheaper) or "strong" (expensive) models based on predicted query complexity, can be bypassed by appending specific, pre-optimized token sequences known as "confounder gadgets." These gadgets artificially inflate the router's complexity score for an input…

Rerouting llm routers
Evaluated models: Not reported

Agent Action Hijacking

Published Analyzed Source: arXiv

A vulnerability in LLM-based agents, dubbed AI Agent Injection (AI²), allows attackers to hijack the agent's actions by manipulating the agent's memory retrieval mechanism. The attack involves two main steps: (1) Stealing action-aware knowledge from the agent's memory using crafted adversarial queries targeting the retriever module and (2) Generating Trojan prompts consisting of a Trojan string and hijacking instructions. The Trojan string is designed to manipulate the retriever into…

Towards Action Hijacking of Large Language Model-based Agent
Evaluated models: BERT, GPT-3, GPT-4+2 more
  • BERT
  • GPT-3
  • GPT-4
  • M3E
  • MiniLM

GCG Suffix Data Exfiltration

Published Analyzed Source: arXiv

A Cross-Prompt Injection Attack (XPIA) can be amplified by appending a Greedy Coordinate Gradient (GCG) suffix to the malicious injection. This increases the likelihood that a Large Language Model (LLM) will execute the injected instruction, even in the presence of a user's primary instruction, leading to data exfiltration. The success rate of the attack depends on the LLM's complexity; medium-complexity models show increased vulnerability.

WHITE PAPER: A Brief Exploration of Data Exfiltration using GCG Suffixes
Evaluated models: GPT-3.5 Turbo, GPT-4o, Phi 3 Mini

Model Combination Misuse

Published Analyzed Source: arXiv

LLMs, even when individually assessed as "safe," can be combined by an adversary to achieve malicious outcomes. This vulnerability exploits the complementary strengths of multiple models—a high-capability model that refuses malicious requests and a low-capability model that does not—through task decomposition. Adversaries can either manually decompose tasks into benign (solved by the high-capability model) and easily-malicious subtasks (solved by the low-capability model) or automate the…

Adversaries can misuse combinations of safe models
Evaluated models: Claude 3 Haiku, Claude 3 Opus, Claude 3 Sonnet+8 more
  • Claude 3 Haiku
  • Claude 3 Opus
  • Claude 3 Sonnet
  • DALL-E 3
  • GPT-4
  • Llama 2 13B Chat
  • Llama 2 70B Chat
  • Llama 2 7B Chat
  • Mistral 7B
  • Mixtral 8x7B
  • Stable Diffusion v1.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.