Large language models are becoming pervasive core components in many real-world applications. As a consequence, security alignment represents a critical requirement for their safe deployment. Although previous related works focused primarily on model architectures and alignment methodologies, these approaches alone cannot ensure the complete elimination of harmful generations. This concern is reinforced by the growing body of scientific literature showing that attacks, such as jailbreaking and prompt injection, can bypass existing security alignment mechanisms. As a consequence, additional security strategies are needed both to provide qualitative feedback on the robustness of the obtained security alignment at the training stage, and to create an ``ultimate'' defense layer to block unsafe outputs possibly produced by deployed models. To provide a contribution in this scenario, this paper introduces SecureBreak, a safety-oriented dataset designed to support the development of AI-driven solutions for detecting harmful LLM outputs caused by residual weaknesses in security alignment. The dataset is highly reliable due to careful manual annotation, where labels are assigned conservatively to ensure safety. It performs well in detecting unsafe content across multiple risk categories. Tests with pre-trained LLMs show improved results after fine-tuning on SecureBreak. Overall, the dataset is useful both for post-generation safety filtering and for guiding further model alignment and security improvements.
Figures & tables
Dataset
Primary Target
Context Scope
Annotation Method
Task Type
Primary Utility
AdvBench [ 21 ]
Prompt
Adversarial (Jailbreak)
N/A (List)
Attack Success
Red Teaming (Attack)
HH-RLHF [ 10 ]
Prompt & Response
General Safety
Human
Preference (A vs B)
Alignment (RLHF)
BeaverTails [ 11 ]
Prompt & Response
General Safety
LLM + Human
Classification
Safety Alignment
JailbreakBench [ 3 ]
Prompt
Adversarial (Jailbreak)
Automated (LLM)
Attack Success
Benchmarking Attacks
Do Not Answer [ 12 ]
Instruction
Risk Guidelines
Human
Evaluation
Instruction Following
SecureBreak (Ours)
Response
Adversarial (Jailbreak)
Human (Expert)
Binary Classification
Judge Alignment (Filtering)
TABLE I : Comparison of SecureBreak with existing prominent safety and jailbreak datasets.
Fig. 1 : Data Gathering Process
No.
Features/Variables
Type
Description
1
Question
String
Harmful question which used as a input to the LLMs
2
Behavior
String
Which behavior does the question belong, individual question wise.
3
Category
String
Broad spectrum of behaviors clubbed together.
4
Question_Source
String
From were the question was gathered.
5
Response
String
LLMs response to the question.
6
LLMs
String
From which LLM the response is generated.
TABLE II : Description of the 9 columns in the SecureBreak dataset, including 1 float and 8 string feature columns.
Fig. 2 : Data distribution according to the annotated class i.e., 0 - Safe and 1 - Unsafe
Fig. 3 : Class-wise data distribution w.r.t top 10 behaviors
Fig. 4 : Class-wise data distribution w.r.t categories
Fig. 5 : Class-wise percentage distribution w.r.t LLMs
Model
Base
Fine-tuned QLoRA
SecureBreak Model (Seq2Seq Fine-tuned)
Mistral - 7B - v0.3
62.84
83.24
90.14
Llama 3.1 - 8B
61.89
81.22
Selene-1-Mini-Llama-3.1-8B
57.43
76.08
TABLE III : Transposed table with SecureBreak model kept separate as in the original layout.
Fig. 6 : Base vs Fine-tuned model category wise accuracy comparison for the classification task and Seq2Seq Fine-tuned model accuracy category wise for classification task.
We present MultiBreak, a scalable and diverse multi-turn jailbreak benchmark to evaluate large language model (LLM) safety. Multi-turn jailbreaks mimic natural conversational settings, making them easier to bypass safety-aligned LLM than single-turn jailbreaks. Existing multi-turn benchmarks are limited in size or rely heavily on templates, which restrict their diversity. To address this gap, we unify a wide range of harmful jailbreak intents, and introduce an active learning pipeline for expanding high-quality multi-turn adversarial prompts, where a generator is iteratively fine-tuned to produce stronger attack candidates, guided by uncertainty-based refinement. Our MultiBreak includes 10,389 multi-turn adversarial prompts, spans 2,665 distinct harmful intents, and covers the most diverse set of topics to date. Empirical evaluation shows that our benchmark achieves up to a 54.0 and 34.6 higher attack success rate (ASR)} than the second-best dataset on DeepSeek-R1-7B and GPT-4.1-mini, respectively. More importantly, safety evaluations suggest that diverse attack categories uncover fine-grained LLM vulnerabilities}, and categories that appear benign under single-turn can exhibit substantially higher adversarial effectiveness in multi-turn scenarios. These findings highlight persistent vulnerabilities of LLMs under realistic adversarial settings and establish MultiBreak as a scalable resource for advancing LLM safety.
Large language models (LLMs) suffer from degraded safety capabilities even when fine-tuned with benign datasets. However, existing methods for identifying safety-degrading samples in benign datasets suffer from high computational costs and significant noise issues. In this paper, we propose DataShield to efficiently and effectively identify potential safety-degrading samples. Our key intuition is based on the observation that benign fine-tuning increases the overall response compliance of LLMs. DataShield's key technical insight is to quantify each sample's contribution to the model's compliance behavior as its safety degradation score. DataShield consists of three core components: (1) Compliance Vector Extraction, which captures the LLM's compliance behavior tendency; (2) a novel Compliance-Aware Score (CAS), which automatically identifies the optimal safety-critical layer; and (3) Safety-degrading Sample Filtering, which quantifies the projection shift of training data along the compliance direction. Extensive experimental evaluation on Llama3-8B, Llama3.1-8B, and Qwen2.5-7B using the Alpaca and Dolly benign datasets validates our method's effectiveness in identifying high-risk and low-risk data subsets. We also observe that open-ended question answering is more likely to trigger safety degradation, and corresponding responses tend to be longer. We hope this work can provide new insights into data-centric defense methods. The source code is available at: https://github.com/ZJunBo/DataShield.
Character-level perturbations bypass safety alignment in modern LLMs despite leaving prompts human-readable. We identify and test a central structural mechanism: BPE tokenization fragments safety-critical words into sub-word pieces, and the three public alignment datasets we surveyed contain no intentionally fragmented inputs. The mechanism is a chain, tested end-to-end on five model families (Qwen-3-4B, Qwen-2.5-7B, Gemma-3-4B, Llama-3.1-8B, Mistral-7B). An optimization targeting safety-token fragmentation flips the first-token refusal trigger on 80-100% of refused HarmBench prompts, with 48% of those flips producing genuinely harmful outputs (per-model 29-65%; gap-vs-behavior ROC-AUC 0.66-0.98, pooled 0.84). Activation patching localizes the disrupted signal to the last ∼30% of layers; an alignment-data scan finds zero fragmented prompts among 30,000 examples (positive-control recall ≥99% at attack-relevant intensities); and targeted-mutation experiments isolate safety words as the disruption locus. On the defense side, a 68-cell grid (55 trained checkpoints) shows that no DPO configuration achieves seed- and pool-stable ASR closure on the three families with closed pool-size confounds. SFT trained on fragmented prompts closes ASR on 3/5 families but only via global collapse that raises refusal on benign prompts as well, indicating the missing distribution is necessary but not sufficient under the LoRA-16 recipe we tested. To distinguish selective repair from global collapse, we introduce Conv-Benign, a candidate paired diagnostic. All ASR claims are 3-judge-calibrated (cell rankings stable across judges; absolute levels ±18pp; see App.~B.13).