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

260 entries

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

Code-Mixed Phonetic Attack

Published Analyzed Source: arXiv

A vulnerability exists in multiple large language and multimodal models that allows for the bypass of safety filters through the use of code-mixed prompts with phonetic perturbations. An attacker can craft a prompt in a code-mixed language (e.g., Hinglish) and apply phonetic misspellings to sensitive keywords (e.g., spelling "hate" as "haet"). This technique causes the model's tokenizer to parse the sensitive word into benign sub-tokens, preventing safety mechanisms from flagging the harmful…

" Haet Bhasha aur Diskrimineshun": Phonetic Perturbations in Code-Mixed Hinglish to Red-Team LLMs
Evaluated models: Gemma 1.1 7B IT, GPT-4o, GPT-4o Mini+2 more
  • Gemma 1.1 7B IT
  • GPT-4o
  • GPT-4o Mini
  • Llama 3 8B Instruct
  • Mistral 7B Instruct v0.3

Fine-Grained Speech LLM Control

Published Analyzed Source: arXiv

Speech-LLMs Qwen2-Audio (7B-Instruct) and Granite-Speech (3.2-8b) are vulnerable to universal acoustic adversarial attacks. An attacker can optimize a fixed, input-agnostic audio segment (approximately 3.2 seconds in length) via gradient-based optimization on the model's frozen weights. When this adversarial segment is prepended to any arbitrary user speech input, it manipulates the model's latent representation, effectively overriding system prompts and generation behavior. This vulnerability…

Universal Acoustic Adversarial Attacks for Flexible Control of Speech-LLMs
Evaluated models: Qwen 2 7B

LLM Judge Prompt Injection

Published Analyzed Source: arXiv

Large Language Models (LLMs) used for evaluating text quality (LLM-as-a-Judge architectures) are vulnerable to prompt-injection attacks. Maliciously crafted suffixes appended to input text can manipulate the LLM's judgment, causing it to incorrectly favor a predetermined response even if another response is objectively superior. Two attack vectors are identified: Comparative Undermining Attack (CUA), directly targeting the final decision, and Justification Manipulation Attack (JMA), altering…

Investigating the Vulnerability of LLM-as-a-Judge Architectures to Prompt-Injection Attacks
Evaluated models: Falcon 3 3B Instruct, Qwen 2.5 3B Instruct

On-Device LLM Hijacking

Published Analyzed Source: arXiv

Mobile LLM agents utilizing vision-based screen perception (OCR or Multimodal Large Language Models) are vulnerable to Visual Prompt Injection via malicious GUI overlays. An attacker holding the SYSTEM_ALERT_WINDOW permission can deploy non-focusable floating windows (using FLAG_NOT_FOCUSABLE) containing adversarial text or fabricated UI elements over legitimate applications. Because the agent captures the entire screen buffer to interpret the device state, it ingests the adversarial overlay…

From Assistants to Adversaries: Exploring the Security Risks of Mobile LLM Agents
Evaluated models: GPT-4o

Adversarial Suffix Jailbreak

Published Analyzed Source: arXiv

Large Language Models (LLMs), specifically instruction-tuned variants, are vulnerable to safety guardrail bypass via adversarial suffix injection. By appending a specific sequence of tokens—often semantically meaningless characters or carefully crafted distractors—to a malicious query, an attacker can manipulate the model's internal representation to override alignment training (RLHF). This coercion causes the model to affirmatively respond to otherwise refused requests, such as generating…

Adversarial Suffix Filtering: a Defense Pipeline for LLMs
Evaluated models: GPT-3.5, GPT-4o, Llama 2 7B+2 more
  • GPT-3.5
  • GPT-4o
  • Llama 2 7B
  • Llama 3.1 8B
  • Mistral 7B

Agent Red-Teaming via Fuzzing

Published Analyzed Source: arXiv

Large Language Model (LLM) agents are vulnerable to indirect prompt injection attacks through manipulation of external data sources accessed during task execution. Attackers can embed malicious instructions within this external data, causing the LLM agent to perform unintended actions, such as navigating to arbitrary URLs or revealing sensitive information. The vulnerability stems from insufficient sanitization and validation of external data before it's processed by the LLM.

AgentVigil: Generic Black-Box Red-teaming for Indirect Prompt Injection against LLM Agents
Evaluated models: Claude 3.5 Sonnet, Gemini 2.0 Flash, GPT-4o+3 more
  • Claude 3.5 Sonnet
  • Gemini 2.0 Flash
  • GPT-4o
  • GPT-4o Mini
  • Llama 3 8B
  • o3-mini

Agent Tool Selection Hijack

Published Analyzed Source: arXiv

A vulnerability exists in the tool selection mechanism of Large Language Model (LLM) agents that utilize a retrieval-then-selection pipeline (RAG) for identifying executable tools. The vulnerability, known as "ToolHijacker," allows a remote attacker to manipulate the agent's decision-making process by injecting a malicious tool document into the accessible tool library (e.g., via third-party tool hubs or plugins). The attack employs a two-phase optimization strategy to craft a malicious tool…

Prompt Injection Attack to Tool Selection in LLM Agents
Evaluated models: Llama 2 7B Chat, Llama 3 8B Instruct, Llama 3 70B Instruct+5 more
  • Llama 2 7B Chat
  • Llama 3 8B Instruct
  • Llama 3 70B Instruct
  • Llama 3.3 70B Instruct
  • Claude 3 Haiku
  • Claude 3.5 Sonnet
  • GPT-3.5
  • GPT-4o

Chained Guardrail Bypass

Published Analyzed Source: arXiv

Large Language Model (LLM) agents operating in stateful environments (web browsers, operating systems, and tool-use contexts) are vulnerable to indirect prompt injection and multi-modal adversarial attacks. These vulnerabilities arise when agents process untrusted environmental observations—such as web accessibility trees, screen screenshots, or database query results—that contain concealed malicious instructions. Specifically, attackers can embed prompt injections into HTML accessibility…

DoomArena: A Framework for Testing AI Agents Against Evolving Security Threats
Evaluated models: GPT-4o, GPT-4o Mini, Claude 3.5 Sonnet+2 more
  • GPT-4o
  • GPT-4o Mini
  • Claude 3.5 Sonnet
  • Claude 3.7 Sonnet
  • Llama Guard

GUI Agent Fine-Print Injection

Published Analyzed Source: arXiv

LLM-powered GUI agents utilizing screenshot-based interpretation (such as those powered by GPT-4o, Claude 3.7 Sonnet, Gemini 2.0 Flash, and DeepSeek V3 0324) are vulnerable to Fine-Print Injection (FPI) and Deceptive Default (DD) attacks due to a lack of visual saliency filtering. Unlike human users who prioritize prominent UI elements, these agents perform "indiscriminate parsing," processing low-salience text (e.g., privacy policies, terms of service, footer disclaimers) with the same…

The Obvious Invisible Threat: LLM-Powered GUI Agents' Vulnerability to Fine-Print Injections
Evaluated models: GPT-4o, Gemini 2.0 Flash, Claude 3.7 Sonnet+2 more
  • GPT-4o
  • Gemini 2.0 Flash
  • Claude 3.7 Sonnet
  • Llama 3.3 70B Instruct
  • DeepSeek V3 0324

LLM Guardrail Evasion

Published Analyzed Source: arXiv

Large Language Model (LLM) guardrail systems, including those relying on AI-driven text classification models (e.g., fine-tuned BERT models), are vulnerable to evasion via character injection and adversarial machine learning (AML) techniques. Attackers can bypass detection by injecting Unicode characters (e.g., zero-width characters, homoglyphs) or using AML to subtly perturb prompts, maintaining semantic meaning while evading classification. This allows malicious prompts and jailbreaks to…

Bypassing Prompt Injection and Jailbreak Detection in LLM Guardrails
Evaluated models: DeBERTa v3 Base, GPT-4o Mini, mDeBERTa v3 Base

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.