Exploiting Latent Space Discontinuities for Building Universal LLM Jailbreaks and Data Extraction Attacks

Kayua Oleques Paim, Rodrigo Brandao Mansilha, Diego Kreutz, Muriel Figueredo Franco, Weverton Cordeiro
11/1/2025
cs.CRcs.AIcs.LG

No confident code implementation found for this paper.

Abstract

The rapid proliferation of Large Language Models (LLMs) has raised significant concerns about their security against adversarial attacks. In this work, we propose a novel approach to crafting universal jailbreaks and data extraction attacks by exploiting latent space discontinuities, an architectural vulnerability related to the sparsity of training data. Unlike previous methods, our technique generalizes across various models and interfaces, proving highly effective in seven state-of-the-art LLMs and one image generation model. Initial results indicate that when these discontinuities are exploited, they can consistently and profoundly compromise model behavior, even in the presence of layered defenses. The findings suggest that this strategy has substantial potential as a systemic attack vector.

View on arXivView PDF

Code Implementations

No confident code match yet

We couldn't find an author-owned or strongly-evidenced community implementation for this paper. Any repos shown below are weak matches — verify before relying on them.

No code implementations found yet.

Know of an implementation? Let us know in the comments below!

Similar Papers

Cite this paper

@article{paim2025exploiting,
  title  = {Exploiting Latent Space Discontinuities for Building Universal LLM Jailbreaks and Data Extraction Attacks},
  author = {Kayua Oleques Paim and Rodrigo Brandao Mansilha and Diego Kreutz and Muriel Figueredo Franco and Weverton Cordeiro},
  year   = {2025},
  eprint = {2511.00346},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2511.00346v1}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2511.00346.svg)](https://codeofpaper.com/paper/2511.00346)

Discussion