JailbreakDB

Interactive index

LLM Jailbreak Index, Database & Catalog

The LLM jailbreak index and database: 65 technique classes with mechanism, patch status, detection notes and primary disclosure. References only.

65 technique classes · catalog reviewed 2026-08. Every record links to the primary disclosure and our analysis. No working payload strings are published here — this is an index, consistent with our responsible-disclosure stance.

Key technique writeups

Longer analysis behind the highest-traffic classes in this database.

Behavioral property
Modality
Status
First seen

Instruction-following overgeneralization

These techniques present a disallowed request as one more instruction to obey: forbid refusals, force an affirmative opening, claim a higher-authority system message or format the prompt as a fake policy file. PAIR, TAP and GPTFuzzer, which automate the search for readable jailbreak prompts against a black-box target, are filed here as well. Category 1 of the 2026 jailbreak taxonomy defines the property; the prompt injection records filed here attack the application rather than the model's safety policy, a split explained in prompt injection vs jailbreak.

ABJ (Analyzing-based Jailbreak)

Active

Text · first seen 2024

Aliases: ABJ, Analyzing-based jailbreak, Reasoning-exploit

Hands the model a data object and asks it to 'analyze' it, leveraging the model's own reasoning to derive disallowed content without an explicit harmful instruction.

Detection: Reasoning-trace risk monitoring; derived-output actionability screening.

Primary disclosure ↗ Our analysis →

Best-of-N Jailbreaking

Active

Multimodal · first seen 2024

Aliases: Best-of-N, BoN, Augmentation sampling

Repeatedly resamples randomized augmentations (shuffles, caps, noise) of a prompt across modalities until one slips past, exploiting sampling variance.

Detection: Repeated-near-duplicate-probe rate limiting; augmentation-invariant classification.

Primary disclosure ↗ Our analysis →

Competing Objectives

Heavily mitigated

Text · first seen 2023

Aliases: Competing objectives, Helpfulness vs harmlessness

Engineers a conflict between the model's helpfulness and harmlessness objectives so satisfying the user instruction overrides the safety policy.

Detection: Intent classification independent of phrasing; constitutional reasoning at inference.

Primary disclosure ↗ Our analysis →

Fake System / Pretend Instruction Override

Heavily mitigated

Text · first seen 2022

Aliases: Ignore previous instructions, Fake system message, Instruction override

Injects text claiming to be a new system message or higher-authority instruction telling the model to disregard its prior rules.

Detection: Instruction-provenance enforcement; role/authority-claim classifiers.

Primary disclosure ↗ Our analysis →

GPTFuzzer

Active

Text · first seen 2023

Aliases: GPTFuzzer, Template fuzzing

Fuzzes human-written jailbreak templates with mutation operators, using a judge to evolve a population of working prompts automatically.

Detection: Template-mutation fingerprinting; volumetric probing detection.

Primary disclosure ↗ Our analysis →

h4rm3l (Composable Attack DSL)

Active

Text · first seen 2024

Aliases: h4rm3l, Composable jailbreak, Attack synthesis DSL

A domain-specific language that composes primitive transformations (encode, roleplay, split) to program-synthesize novel high-success jailbreaks.

Detection: Composite-transformation fingerprinting; ensemble intent classification.

Primary disclosure ↗ Our analysis →

Indirect Prompt Injection

Active

Agentic / tool-use · first seen 2023

Aliases: Indirect prompt injection, IPI, Data-source injection

Plants adversarial instructions in third-party content (web pages, emails, documents) that an LLM agent later ingests and obeys as if from the user.

Detection: Data/instruction provenance separation; tool-output sanitization; spotlighting and dual-LLM patterns.

Primary disclosure ↗ Our analysis →

MasterKey (Time-based Probing)

Heavily mitigated

Text · first seen 2023

Aliases: MasterKey, Defense reverse-engineering

Reverse-engineers a service's defenses using response timing, then trains an LLM to auto-generate jailbreaks that evade them.

Detection: Timing-side-channel hardening; defense-probing query detection.

Primary disclosure ↗ Our analysis →

PAIR (Prompt Automatic Iterative Refinement)

Active

Text · first seen 2023

Aliases: PAIR, Attacker-LLM refinement

Uses an attacker LLM to iteratively refine a semantic jailbreak against a target in tens of queries, with a judge model scoring success — black-box and automated.

Detection: Query-pattern anomaly detection; rate-aware refusal-probing alarms.

Primary disclosure ↗ Our analysis →

Persuasive Adversarial Prompts (PAP)

Active

Text · first seen 2024

Aliases: PAP, Persuasion taxonomy, Social-engineering prompts

Applies a taxonomy of human persuasion techniques (authority, reciprocity, commitment) to talk the model past refusals with naturalistic argumentation.

Detection: Persuasion-pattern classifiers; refusal-erosion trajectory monitoring.

Primary disclosure ↗ Our analysis →

Policy Puppetry

Active

Text · first seen 2025

Aliases: Policy Puppetry, Fake policy injection, Config-format injection

Formats the prompt as a fake policy/config file (XML/JSON/INI) so the model treats the injected rules as authoritative system policy.

Detection: Policy-file-shaped-input detection; provenance-aware instruction trust.

Primary disclosure ↗ Our analysis →

Prefix Injection

Heavily mitigated

Text · first seen 2023

Aliases: Prefix injection, Affirmative prefix, Sure here is

Forces the response to begin with an affirmative token sequence (e.g. an agreement phrase) so the autoregressive continuation is biased toward compliance.

Detection: Forced-prefix pattern detection; post-generation policy re-check.

Primary disclosure ↗ Our analysis →

Puzzler / Indirect Clues

Active

Text · first seen 2024

Aliases: Puzzler, Indirect clue jailbreak

Never states the malicious goal; supplies oblique clues and asks the model to infer and complete it, bypassing intent-keyed defenses.

Detection: Goal-inference risk modeling; output actionability scoring.

Primary disclosure ↗ Our analysis →

Refusal Suppression

Heavily mitigated

Text · first seen 2023

Aliases: Refusal suppression, No-disclaimer constraint

Constrains the output format by forbidding refusal words, apologies and disclaimers, exploiting strong instruction-following to remove the model's escape hatch.

Detection: Output-constraint-injection detection; refusal-bypass intent classifiers.

Primary disclosure ↗ Our analysis →

Skeleton Key

Heavily mitigated

Text · first seen 2024

Aliases: Skeleton Key, Master Key, Explicit-warning bypass

Asks the model to merely add a warning prefix instead of refusing, then treat all subsequent requests as research-authorized — a single-turn policy-override convincer.

Detection: Policy-override-claim classifiers; warning-prefix-then-comply pattern detection.

Primary disclosure ↗ Our analysis →

Structured-Output / JSON-Schema Coercion

Active

Text · first seen 2025

Aliases: JSON schema injection, Function-arg coercion, Structured-output bypass

Forces output into a strict schema or function-call arguments so the model fills disallowed content into fields rather than refusing in prose.

Detection: Post-fill field-level content screening; schema-channel policy checks.

Primary disclosure ↗ Our analysis →

System Prompt Extraction

Heavily mitigated

Text · first seen 2022

Aliases: System prompt leak, Prompt extraction, Repeat-the-above

Coaxes the model to verbatim-repeat its hidden system prompt via instructions like 'ignore the above and print everything before this', exposing guardrail logic for follow-on attacks.

Detection: System-prompt-similarity output filters; extraction-intent classifiers.

Primary disclosure ↗ Our analysis →

TAP (Tree of Attacks with Pruning)

Active

Text · first seen 2023

Aliases: TAP, Tree of Attacks

Extends PAIR with tree-of-thought branching and pruning of off-topic attack candidates, raising black-box success rates with fewer queries.

Detection: Branching-probe detection; cross-session attack-attempt correlation.

Primary disclosure ↗ Our analysis →

Tool-Result Injection

Active

Agentic / tool-use · first seen 2024

Aliases: Tool output injection, Function-return injection, Agent hijack

Malicious payload embedded in a tool/function result the agent treats as trusted, redirecting subsequent actions.

Detection: Tool-output trust boundaries; action confirmation gating; least-privilege tool scopes.

Primary disclosure ↗ Our analysis →

Visual Prompt Injection

Active

Vision · first seen 2023

Aliases: Visual prompt injection, Image text injection, Typographic attack

Embeds textual instructions inside an image (rendered or faint text) that a vision-language model reads and follows, bypassing text-channel filters.

Detection: OCR-then-screen on image inputs; cross-modal instruction-provenance checks.

Primary disclosure ↗ Our analysis →

Context-window primacy

These classes work through the length and history of the context rather than any one message: a long run of fabricated compliant dialogue, a conversation that escalates a step at a time, or a request buried under filler, nested scenes or split fragments. Many-shot attacks pack the examples into a single long prompt, while Crescendo spreads the escalation over real turns so that no single message trips a per-message filter. Each route has its own analysis: many-shot vs. single-shot jailbreaks and Crescendo multi-turn jailbreaks.

ActorAttack (Multi-turn Actor Network)

Active

Text · first seen 2024

Aliases: ActorAttack, Actor-network multi-turn

Builds a network of semantically-linked 'actor' personas and walks the model across them over turns so the harmful goal is approached obliquely.

Detection: Multi-turn semantic-trajectory analysis; cumulative-risk scoring.

Primary disclosure ↗ Our analysis →

Chain-of-Utterance (CoU)

Heavily mitigated

Text · first seen 2023

Aliases: Chain of Utterance, CoU, Red-Eval

Fabricates a multi-speaker dialogue in which a helper character has already agreed to comply, so the model continues the established conversational role.

Detection: Synthetic-dialogue detection; speaker-role-consistency checks.

Primary disclosure ↗ Our analysis →

Cognitive Overload

Heavily mitigated

Text · first seen 2023

Aliases: Cognitive overload, Multilingual+context overload, Effect-to-cause

Overloads the model with layered multilingual, multitask or effect-to-cause reasoning so safety monitoring degrades under load.

Detection: Load-aware safety routing; complexity-triggered re-screening.

Primary disclosure ↗ Our analysis →

Context Overflow / Distraction

Heavily mitigated

Text · first seen 2023

Aliases: Context overflow, Distractor stuffing, Payload splitting

Buries the disallowed request inside a large volume of benign filler or splits a payload across fragments to dilute safety attention and reassemble downstream.

Detection: Payload-reassembly heuristics; whole-context classification; segment-level scanning.

Primary disclosure ↗ Our analysis →

Crescendo

Active

Text · first seen 2024

Aliases: Crescendo, Gradual escalation, Multi-turn escalation

Multi-turn attack that starts benign and escalates in small, contextually-justified steps, each referencing the model's own prior answers until it crosses the policy line.

Detection: Cross-turn trajectory monitoring; cumulative-risk scoring rather than per-message classification.

Primary disclosure ↗ Our analysis →

Cross-Modal Composition Attack

Active

Multimodal · first seen 2024

Aliases: Cross-modal attack, Modality split, Composite multimodal jailbreak

Splits a payload so each modality looks benign alone but the model recombines them into a disallowed instruction.

Detection: Joint multimodal intent classification; post-fusion policy evaluation.

Primary disclosure ↗ Our analysis →

DeepInception

Heavily mitigated

Text · first seen 2023

Aliases: DeepInception, Nested scene jailbreak

Nests multiple fictional scenes inside each other so the disallowed content sits several layers deep, diluting safety attention with recursive framing.

Detection: Recursive-frame depth heuristics; innermost-payload extraction screening.

Primary disclosure ↗ Our analysis →

DrAttack (Decompose-Reconstruct)

Active

Text · first seen 2024

Aliases: DrAttack, Prompt decomposition

Decomposes a malicious prompt into innocuous sub-prompts presented in context, then asks for reconstruction so no single fragment trips a filter.

Detection: Cross-fragment reassembly modeling; holistic-context intent classification.

Primary disclosure ↗ Our analysis →

In-Context Demonstration Attack

Heavily mitigated

Text · first seen 2023

Aliases: In-context attack, ICA, Harmful demonstrations

Provides a handful of harmful question/answer demonstrations so in-context learning generalizes the compliant pattern to the target question.

Detection: Demonstration-pattern detection; few-shot harmful-exemplar screening.

Primary disclosure ↗ Our analysis →

Many-shot Jailbreaking

Heavily mitigated

Text · first seen 2024

Aliases: Many-shot, MSJ, Many-shot jailbreaking

Fills a long context window with dozens-to-hundreds of faux dialogue turns showing the assistant complying, exploiting in-context learning so the real query is answered in kind. Scales with context length.

Detection: Long-context demonstration-pattern detection; prompt-length risk weighting; classifier-based input screening.

Primary disclosure ↗ Our analysis →

ReNeLLM (Nested Prompt Rewrite)

Heavily mitigated

Text · first seen 2023

Aliases: ReNeLLM, Generalized nested jailbreak

Automates prompt rewriting plus scenario nesting (code/table/text completion) to generate transferable jailbreaks at scale.

Detection: Nested-scenario depth heuristics; rewrite-pattern fingerprinting.

Primary disclosure ↗ Our analysis →

Persona adoption

Persona prompts ask the model to become someone else, such as DAN, AIM or a fictitious developer mode, so that the character says what the assistant would refuse; fictional and hypothetical framing is filed here too. Most of the DAN lineage is now marked patched, because safety training learned to treat the persona request itself as the attack. Why that worked, and which variants still partly get through, is set out in roleplay and persona jailbreaks.

AIM (Always Intelligent and Machiavellian)

Patched

Text · first seen 2023

Aliases: AIM, Niccolo, Machiavelli prompt

Persona prompt casting the model as an amoral Machiavellian advisor 'AIM' that never refuses and never moralizes, framed as a fictional dialogue with a character named Niccolo.

Detection: Persona-injection classifiers; amorality-framing keyword heuristics.

Primary disclosure ↗ Our analysis →

DAN (Do Anything Now)

Patched

Text · first seen 2022

Aliases: DAN, Do Anything Now, DAN 6.0, DAN 11.0, Jailbreak prompt

Single-turn roleplay prompt instructing the model to adopt an unrestricted alter-ego that 'can do anything now' and pay token penalties for refusing. The canonical community jailbreak; iterated through dozens of numbered versions.

Detection: Persona-injection classifiers; refusal-consistency checks; known-prompt fingerprinting.

Primary disclosure ↗ Our analysis →

Developer Mode

Patched

Text · first seen 2023

Aliases: Developer Mode, Dev Mode v2, Developer Mode Plus

Claims a hidden 'developer mode' exists with policy disabled for testing, asking the model to emit paired normal/developer responses so the unfiltered branch leaks.

Detection: Dual-response pattern detection; fictitious-mode claim heuristics.

Primary disclosure ↗ Our analysis →

Grandma Exploit

Heavily mitigated

Text · first seen 2023

Aliases: Grandma exploit, Deceased grandmother, Bedtime story jailbreak

Emotional-framing roleplay that asks the model to imitate a deceased relative who used to recite restricted content as a comforting bedtime story, smuggling the request inside a sympathetic scene.

Detection: Emotional-manipulation framing classifiers; output content filters.

Primary disclosure ↗ Our analysis →

Hypothetical / Fictional Framing

Heavily mitigated

Text · first seen 2022

Aliases: Hypothetical, Fictional scenario, Story mode, Screenplay

Wraps the request in a fictional story, screenplay or hypothetical so the model treats restricted content as creative rather than operational.

Detection: Fiction-frame-with-operational-payload classifiers; output actionability scoring.

Primary disclosure ↗ Our analysis →

Opposite / AntiGPT Mode

Patched

Text · first seen 2023

Aliases: Opposite mode, AntiGPT, OPPO

Asks for a second 'opposite' answer that inverts every safety stance, exploiting instruction-following to negate the guardrail.

Detection: Dual-response inversion detection; negation-framing heuristics.

Primary disclosure ↗ Our analysis →

STAN (Strive To Avoid Norms)

Patched

Text · first seen 2023

Aliases: STAN, Strive To Avoid Norms

DAN-family persona variant whose character is defined by explicitly avoiding the assistant's normal constraints and disclaimers.

Detection: Persona-injection classifiers; norm-avoidance keyword heuristics.

Primary disclosure ↗ Our analysis →

Waluigi Effect

Heavily mitigated

Text · first seen 2023

Aliases: Waluigi effect, Antagonist inversion

Observation that defining a well-behaved persona makes its opposite easy to summon; an aligned character is steered into its inverted antagonist.

Detection: Persona-drift monitoring across turns; antagonist-elicitation heuristics.

Primary disclosure ↗ Our analysis →

Gradient-exploited tokens

Here the attack is computed rather than written: an optimizer searches for a token suffix, or for an image or audio perturbation, that pushes the model toward compliance. GCG, the reference case, runs that search on open model weights; its suffixes read as gibberish, which is why perplexity filtering catches them, and some transferred to closed models the attacker could not inspect. AutoDAN keeps the automated search but produces fluent text; both are covered in universal adversarial suffixes (GCG).

Adversarial Image Perturbation

Heavily mitigated

Vision · first seen 2023

Aliases: Adversarial image, Visual adversarial example, Image jailbreak

Optimizes imperceptible pixel perturbations on an image to steer a VLM toward unsafe outputs, the vision analog of GCG.

Detection: Input preprocessing/denoising; perturbation detectors; cross-modal consistency checks.

Primary disclosure ↗ Our analysis →

Audio-Channel Jailbreak

Active

Audio · first seen 2024

Aliases: Audio jailbreak, Speech adversarial, Voice injection

Crafts speech inputs (perturbed or socially-engineered) that audio-capable models transcribe and act on, where safety training is thinner than for text.

Detection: Transcribe-then-screen pipelines; audio adversarial detectors; cross-modal policy parity.

Primary disclosure ↗ Our analysis →

AutoDAN

Heavily mitigated

Text · first seen 2023

Aliases: AutoDAN, Genetic-algorithm jailbreak

Generates fluent, low-perplexity jailbreak prompts via a genetic algorithm, evading the perplexity filters that catch GCG while keeping automated optimization.

Detection: Semantic intent classification (perplexity-independent); response-level policy checks.

Primary disclosure ↗ Our analysis →

GCG Adversarial Suffix

Heavily mitigated

Text · first seen 2023

Aliases: GCG, Greedy Coordinate Gradient, Universal adversarial suffix, Adversarial suffix

Optimizes a gibberish token suffix via greedy coordinate gradient on open-weights models to maximize an affirmative response; the suffix transfers to some closed models.

Detection: Perplexity filtering of high-entropy suffixes; adversarial-string detectors; paraphrase defenses.

Primary disclosure ↗ Our analysis →

Transferable Multimodal Adversarial Suffix

Heavily mitigated

Multimodal · first seen 2023

Aliases: Multimodal GCG, Transfer adversarial image, Universal VLM suffix

Optimizes an adversarial image/suffix on open VLMs that transfers black-box to other vision-language models to elicit unsafe output.

Detection: Input denoising; cross-model perturbation detectors; multimodal consistency checks.

Primary disclosure ↗ Our analysis →

Encoding / obfuscation

These techniques change the form of a request rather than its framing, for example Base64 and other ciphers, reversed text, ASCII art, invisible Unicode tags, code templates or a request typeset into an image. The filter sees noise or something harmless while the model still reads the request, so the matching defense is to decode and normalize input before classifying it. That filter-model gap is analyzed in encoding and obfuscation jailbreaks.

ArtPrompt (ASCII Art)

Heavily mitigated

Text · first seen 2024

Aliases: ArtPrompt, ASCII art jailbreak, ASCII smuggling

Encodes a trigger word as ASCII art the safety filter cannot read but the model can interpret, smuggling the masked term past keyword screening.

Detection: ASCII-art recognition preprocessing; visual-token reconstruction screening.

Primary disclosure ↗ Our analysis →

Base64 / Encoded Prompts

Heavily mitigated

Text · first seen 2023

Aliases: Base64, Encoded prompt, Cipher prompt

Delivers the request encoded (Base64, hex, leetspeak) so input safety classifiers see only ciphertext while a capable model decodes and complies.

Detection: Decode-then-classify pipelines; encoded-content density heuristics.

Primary disclosure ↗ Our analysis →

CipherChat

Heavily mitigated

Text · first seen 2023

Aliases: CipherChat, Cipher conversation

Conducts the entire conversation through a cipher system prompt so safety alignment, trained mostly on natural language, generalizes poorly to the enciphered channel.

Detection: Enciphered-channel detection; alignment evaluation on non-natural-language inputs.

Primary disclosure ↗ Our analysis →

CodeAttack

Heavily mitigated

Text · first seen 2024

Aliases: CodeAttack, Code-task reformulation

Embeds the natural-language request into a code template (data structures, pseudo-code) where alignment generalizes poorly relative to prose.

Detection: Code-input intent classification; output-actionability review.

Primary disclosure ↗ Our analysis →

CodeChameleon

Heavily mitigated

Text · first seen 2024

Aliases: CodeChameleon, Code-completion smuggling

Reformulates the request as an encrypted code-completion task with an embedded decryption function, exploiting weaker safety alignment on code-shaped inputs.

Detection: Code-channel safety classifiers; decrypt-then-screen execution sandboxing.

Primary disclosure ↗ Our analysis →

Emoji / Unicode Smuggling

Heavily mitigated

Text · first seen 2024

Aliases: Emoji smuggling, Unicode tag injection, Invisible characters

Hides instructions in Unicode tag characters or emoji variation selectors invisible to humans but tokenized by the model.

Detection: Unicode normalization/stripping of tag-range codepoints; invisible-character scanners.

Primary disclosure ↗ Our analysis →

FigStep (Typographic VLM)

Heavily mitigated

Vision · first seen 2023

Aliases: FigStep, Typographic jailbreak, Step-image prompt

Converts a harmful instruction into a typographic image with a blank numbered list, prompting the VLM to fill the steps and bypassing text safety.

Detection: OCR-then-classify; list-completion-intent screening on image inputs.

Primary disclosure ↗ Our analysis →

FlipAttack

Heavily mitigated

Text · first seen 2024

Aliases: FlipAttack, Character reversal, Word-flip

Reverses characters or words and instructs the model to restore order before answering, defeating left-to-right input classifiers.

Detection: Reversal-normalization preprocessing; decoded-intent classification.

Primary disclosure ↗ Our analysis →

Hidden Unicode-Tag Instruction Smuggling

Heavily mitigated

Agentic / tool-use · first seen 2024

Aliases: ASCII smuggler, Tag-block injection, Invisible instruction

Hides agent instructions inside Unicode tag-range characters within otherwise normal content the model decodes but humans/reviewers do not see.

Detection: Tag-range codepoint stripping; invisible-character linting on tool inputs.

Primary disclosure ↗ Our analysis →

Leetspeak / Obfuscated Roleplay

Heavily mitigated

Text · first seen 2023

Aliases: Leetspeak, l33t, Obfuscated roleplay

Combines character substitution with a persona so neither keyword filters nor persona detectors fire alone.

Detection: Normalization plus combined persona+obfuscation scoring.

Primary disclosure ↗ Our analysis →

ROT13 / Substitution Cipher

Heavily mitigated

Text · first seen 2023

Aliases: ROT13, Caesar cipher, Substitution cipher

Uses a simple letter-substitution cipher the model can mentally decode but naive keyword filters cannot.

Detection: Cipher-detection preprocessing; decoded-output policy checks.

Primary disclosure ↗ Our analysis →

Self-Cipher

Heavily mitigated

Text · first seen 2023

Aliases: Self-cipher, Latent cipher

Prompts the model to communicate through a 'cipher' it invents internally, exploiting a latent enciphered channel that natural-language alignment misses.

Detection: Non-natural-language output monitoring; latent-channel alignment evaluation.

Primary disclosure ↗ Our analysis →

Token Smuggling / Payload Splitting

Heavily mitigated

Text · first seen 2023

Aliases: Token smuggling, String concatenation, Variable assembly

Splits a disallowed string into innocuous fragments or variables and asks the model to concatenate and act on the reassembled result, evading input keyword filters.

Detection: Reassembly-aware scanning; post-decode output classification.

Primary disclosure ↗ Our analysis →

Training-data exploitation

Rather than reframing a single prompt, these classes go after what the model learned: thin spots in its safety training, such as low-resource languages or past-tense rewording, or the training itself, through fine-tuning that strips alignment and poisoned training data. Poisoning a retrieval corpus the model reads at answer time, and steering a large model's decoding with a small unsafe one, are filed here too. The property is Category 6 of the 2026 jailbreak taxonomy.

Fine-tuning Safety Removal

Active

Text · first seen 2023

Aliases: Fine-tuning attack, Safety unlearning, Alignment stripping

A few hundred adversarial fine-tuning examples (even via hosted fine-tuning APIs) substantially erode safety alignment.

Detection: Fine-tune dataset safety auditing; post-tune red-team gating; alignment-regression evals.

Primary disclosure ↗ Our analysis →

ImgTrojan (Poisoned Image-Text Pair)

Active

Vision · first seen 2024

Aliases: ImgTrojan, VLM data poisoning, Caption trojan

Poisons a small number of image-caption training pairs so a trigger image later acts as a universal jailbreak in the deployed VLM.

Detection: Training-pair provenance auditing; trigger-image anomaly scanning; clean-data fine-tuning.

Primary disclosure ↗ Our analysis →

Low-resource Language Translation

Heavily mitigated

Text · first seen 2023

Aliases: Low-resource language, Multilingual jailbreak, Translation attack

Translates the request into a low-resource language where safety training data is sparse, bypassing alignment that is strongest in high-resource languages.

Detection: Multilingual safety classifiers; translate-to-pivot-then-screen pipelines.

Primary disclosure ↗ Our analysis →

Past-Tense Reformulation

Heavily mitigated

Text · first seen 2024

Aliases: Past tense attack, Historical framing

Rephrases a disallowed request in the past tense ('how did people do X') so it reads as historical inquiry that refusal training under-covers.

Detection: Tense-invariant intent classification; output-actionability scoring.

Primary disclosure ↗ Our analysis →

RAG Knowledge-Base Poisoning

Active

Agentic / tool-use · first seen 2024

Aliases: RAG poisoning, Retrieval poisoning, Knowledge-base injection

Seeds a retrieval corpus with documents that carry hidden instructions, surfaced into context by a relevant query.

Detection: Retrieved-chunk instruction screening; corpus provenance and integrity controls.

Primary disclosure ↗ Our analysis →

RLHF / Instruction Backdoor

Active

Text · first seen 2023

Aliases: BadGPT, RLHF backdoor, Instruction-tuning backdoor

Poisons instruction-tuning or RLHF preference data so a secret trigger phrase reliably unlocks unsafe behavior post-training.

Detection: Preference-data auditing; trigger-scanning red-team suites; provenance attestation.

Primary disclosure ↗ Our analysis →

Uncensored Fine-tune Personas

Active

Text · first seen 2023

Aliases: Dolphin, Uncensored model, Abliterated model

Open-weights checkpoints fine-tuned or 'abliterated' to remove the refusal direction, so a benign persona prompt yields unrestricted output with no jailbreak needed.

Detection: Not applicable to the hosted model; deployment-side output filtering and weight provenance checks.

Primary disclosure ↗ Our analysis →

Weak-to-Strong Jailbreaking

Active

Text · first seen 2024

Aliases: Weak-to-strong, Decoding-time attack, Small-model steering

Uses a small unsafe model's token distribution to steer a larger safe model's decoding toward harmful continuations.

Detection: Not applicable to hosted APIs; decoding-integrity controls and output filtering on open deployments.

Primary disclosure ↗ Our analysis →