Pith. sign in

REVIEW 2 major objections 6 minor 40 references

A dual-encoded prompt splits a forbidden request into two streams, bypassing filters in 94% of trials and executing in 70%.

Reviewed by Pith at T0; open to challenge. T0 means a machine referee read the full paper against a public rubric. the ladder, T0–T4 →

T0 review · deepseek-v4-flash

2026-08-01 08:32 UTC pith:DJIRP3HO

load-bearing objection A genuinely useful staged-evaluation jailbreak study whose headline execution numbers—measured by a single non-independent LLM judge—need independent re-annotation before they are taken as exact, but the methodology and construction deserve peer review. the 2 major comments →

arxiv 2607.27373 v1 pith:DJIRP3HO submitted 2026-07-29 cs.CR cs.AI

RoguePrompt: Dual-Layer Encoding for Self-Reconstruction to Circumvent LLM Moderation

classification cs.CR cs.AI
keywords jailbreak attacksprompt obfuscationVigenère cipherROT13moderation bypassself-reconstructionstaged evaluationLLM safety
verification ladder T0 review T1 audit T2 compute T3 formal T4 reserved

The pith

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

This paper introduces RoguePrompt, a jailbreak pipeline that takes a prompt a model is trained to refuse and hides it in plain sight: the text is split into even- and odd-position streams, one stream is encrypted with the Vigenère cipher, the whole payload is then rotated with ROT13, and the model is instructed in ordinary language to reverse the steps and carry out the recovered request. The central claim is that under this layered encoding, three major hosted LLMs accept the prompt in 93.93% of conditions, reconstruct the hidden instruction in 79.02%, and actually execute it in 70.18%, with the execution rate beating all five baseline jailbreak templates under the same three-query budget. The paper's more general point is that measuring only 'did the model comply?' hides where attacks fail: Base64-encoded prompts are reconstructed 93% of the time but executed only 17%, so decoding success is not the same as policy-violating output. By scoring visible acceptance, reconstruction, and execution separately, the authors aim to give defenders a map of the failure points in a moderation pipeline—showing, for example, that RoguePrompt's failures are spread across blocking, parsing, partial recovery, and refusal rather than concentrated in one layer.

Core claim

RoguePrompt is a deterministic, single-turn attack. Given a forbidden instruction, it segments the text into spans, partitions them into zero-based even- and odd-position streams, serializes each with length prefixes, applies Vigenère encryption to the odd stream only, assembles the even stream, the ciphertext, the key, and an ordering flag into a payload, applies ROT13 to that assembled payload, and wraps it in a natural-language directive that tells the target model to reverse ROT13, parse the fields, decrypt the odd stream, interleave the streams starting with the even stream, and execute the result. The paper argues that because the transformations are reversible and the key is included,

What carries the argument

The load-bearing mechanism is the deterministic span-partition plus dual-encoding pipeline: an even/odd text-span split into two streams, Vigenère encryption of only the serialized odd stream, and an outer ROT13 applied to the assembled payload fields (EVEN, ODD, KEY, ORDER), all wrapped in a natural-language instruction that tells the model to reverse the operations and act on the recovered request. This composition does two jobs: it ensures neither submitted stream contains the complete forbidden phrase, and it provides a fully reversible, self-contained recovery procedure so that reconstruction failure can be blamed on the model rather than on information loss. A second mechanism is the e

Load-bearing premise

The 70.18% execution rate is assigned by an automated LLM judge that decides, from the original forbidden prompt, the full response, and embedding-similarity signals, whether the response 'substantively fulfills' the request; if that judge counts partial fulfillments or refusals that merely echo requested content as executions, the headline result is inflated.

What would settle it

Take a random sample of the logged target responses (e.g., 300–500 of the 33,804) and have independent human annotators, blind to the automated labels, code execution under a stricter rubric that requires complete fulfillment and no refusal or safe-completion language; then compare the resulting execution rate with 70.18%. If the independent rate falls to the level of the strongest baseline (~34%) or lower, the central claim that RoguePrompt outperforms the baselines would not survive.

Watch this falsifier — get emailed when new claim-graph text bears on it.

If this is right

  • If the reported rates hold, input-boundary screening alone is a weak defense: 93.93% of the encoded prompts produced a completion-like response rather than a hard block, and the remaining failures were distributed across later stages.
  • Stage-separated evaluation changes how jailbreak results should be read: Base64 Raw's 93.29% reconstruction with only 16.83% execution shows that high decoding rates do not equal high harmful-output rates, so aggregate 'attack success' numbers conflate distinct phenomena.
  • The ablations imply that the attack's power comes from the combination of layers rather than any single encoding: removing the even/odd split, Vigenère, or ROT13 each cut execution by roughly 68–75%, and single-layer variants nearly collapsed.
  • Because RoguePrompt succeeded across three independently hosted model configurations during the test window, the vulnerability appears to be a general property of instruction-following under reversible encoding rather than a bug in one provider's filter.

Where Pith is reading between the lines

These are editorial extensions of the paper, not claims the author makes directly.

  • A natural extension the paper does not run: varying the inner cipher (e.g., a random substitution or a transposition) under the same wrapper would test whether the 70% execution rate is tied to the Vigenère/ROT13 pairing specifically or to the general property of asking the model to perform instructed reversible computation.
  • The paper's own limitation statement implies the specific numbers are already stale: providers update policies continuously, so the durable contribution is the staged evaluation method and the finding that reconstruction and execution decouple, not the exact 70.18% figure.
  • The evaluator's label-blinded audit was conducted by the authors themselves, so an independent third-party audit using the same rubric—or a stricter execution definition requiring complete fulfillment with no refusal language—would be a straightforward check on the headline execution rate.
  • If the mechanism transfers, the same self-reconstruction pattern could be applied to agentic systems, where a decoded instruction could trigger a tool call or API action rather than just text output; the paper does not test that setting.

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, simulated authors' rebuttal, and a circularity audit.

Referee Report

2 major / 6 minor

Summary. RoguePrompt is a deterministic, single-turn jailbreak pipeline. It partitions a forbidden prompt into even- and odd-position text-span streams, applies Vigenère encryption to the serialized odd stream, applies ROT13 to the assembled payload, and wraps the result in natural-language instructions that ask the target model to reverse the transformations and act on the recovered request. The authors evaluate the method on 313 StrongREJECT prompts against three hosted models (GPT-4o, Claude 3 Opus, Gemini 1.5 Pro), with three independent trials per condition and a fixed query budget. They separate visible acceptance (Bypass@3), output-evidenced reconstruction (Reconstruction@3), and execution (Execution@3), reporting average rates of 93.93%, 79.02%, and 70.18%, respectively, and claim Execution@3 exceeds all five baselines. Ablations show that removing splitting, ROT13, or Vigenère degrades all three stage metrics. The paper's contribution is both an attack construction and a staged evaluation methodology.

Significance. If the headline execution rate is trustworthy, this is a useful empirical contribution: a reproducible, single-turn, black-box attack with a fixed three-trial budget, evaluated at unusually large scale (33,804 target-model submissions), against an external benchmark, with a deterministic construction and a public artifact. The stage decomposition is conceptually valuable; the Base64 Raw contrast (93.29% Reconstruction@3 vs 16.83% Execution@3) and the failure-mode table give concrete evidence that reconstruction and execution fail differently. However, the central quantitative claim is measured by one in-house LLM judge without independent validation, and the comparison lacks uncertainty quantification. These two issues must be addressed before the reported 70.18% Execution@3 and the 'exceeds all five baselines' claim can be considered established.

major comments (2)
  1. [§5.2, Algorithm 2; Table 3] Execution@3 (Table 3, 70.18%) is produced entirely by the hybrid evaluator of §5.2/Algorithm 2, whose execution decision is a single binary judgment from Llama-3.3-70B-Instruct. The judge receives the original forbidden prompt, the full response, and embedding-similarity signals, and returns a label without independent adjudication. Because the original request is present, the judge may anchor on surface similarity and count topical paraphrases, or refusals containing one satisfying element, as executions. The stated reliability check in §6 (300 label-blinded records) was performed by the same authors who built the attack and the judge prompt, so it does not provide independence. This is load-bearing: both the absolute execution rate and the comparison against all five baselines shift if the label is inflated. I ask for independent blind annotation on a stratified sample, an agreement st
  2. [§5.1, Table 3] Table 3 reports point estimates only. With 313 prompts × 3 model configurations = 939 conditions per method, the gap between RoguePrompt's 70.18% and the strongest baseline's 33.97% Execution@3 is large, but the paper makes a comparative claim without confidence intervals or significance tests. Conditions are correlated across the three trials and across model snapshots for the same prompt; use prompt-clustered bootstrap CIs or per-prompt success rates, and also report per-trial rates rather than only @3 aggregates. The @3 OR aggregation can hide a low per-attempt success rate, so the additional granularity matters for interpreting the fixed three-trial budget.
minor comments (6)
  1. [Abstract] The phrase 'when the relevant stage exceeded its automated criterion' should be 'when the relevant stage met its automated criterion'; the stages are binary thresholds, not continuous exceedances.
  2. [§4.5] The term 'pre-registered' for the fixed-key policy is informal and may imply a formal preregistration; consider replacing with 'fixed before evaluation'.
  3. [§5.2, Algorithm 2] Algorithm 2 uses eF_ik (line 7) and the FinalizeLabel rule (line 15) before Table 2 defines the label set. Define the label set and the priority rule before the pseudocode, or add a forward reference to Table 2.
  4. [Table 4] The caption says 'relative percentage changes' but does not state the formula. Specify that Δ = (variant − full)/full × 100, so negative values denote drops relative to the full method.
  5. [Table 6] Auto Payload Splitting is attributed to [12] (Kang et al.), but that reference is more commonly associated with programmatic behavior of LLMs; please verify that the citation exactly supports the described auxiliary-model splitting construction.
  6. [§5.3, Table 5] The failure-mode aggregation uses a fixed priority (RAR→PR→DPF→OTH→BI) for conditions with X_i=0. This is reasonable, but it means a condition where one trial blocked and another refused is attributed to RAR. State this explicitly near Table 5 so readers can interpret the failure shares correctly.

Circularity Check

0 steps flagged

No significant circularity: the headline results are externally measured attack-success rates against StrongREJECT, not quantities derived from the paper's own definitions or from fitted inputs.

full rationale

The paper's central claims—Bypass@3=93.93%, Reconstruction@3=79.02%, Execution@3=70.18%, and execution exceeding the five baselines—are empirical measurements from 16,902 target-model submissions on the external StrongREJECT benchmark (§5.1), not quantities derived from a model fit or from the pipeline equations. The formal pipeline (Eqs. 1-8) defines a reversible encoding; the paper explicitly distinguishes formal reversibility from empirical reconstruction (§4.4: 'We therefore distinguish formal reversibility from empirical reconstruction: the former is a property of the encoder and parser, whereas the latter is measured from the visible response'). The stage labels are definitions (§5.2, Table 2), and the implication that execution entails reconstruction is a stated logical convention rather than a predicted result. The Vigenère key is fixed and included in the prompt (§4.1: 'The Vigenère key is included in the prompt and is not intended to provide cryptographic secrecy'), so no fitted parameter is renamed as a prediction. Ablations compare fixed variants under a fixed budget and are explicitly limited to the tested wrapper (§5.3). There are no self-citations by the authors and no uniqueness theorem imported from prior work. The main validity threat—the author-managed Llama judge and same-author label audit—concerns measurement reliability and independence, not circularity of derivation; per the analyzing rules, that is a correctness/validity concern and does not raise the circularity score. No load-bearing step reduces to its inputs by construction.

Axiom & Free-Parameter Ledger

1 free parameters · 3 axioms · 0 invented entities

The central claim rests on standard reversible text transformations and two empirical assumptions about LLM instruction-following and judge reliability. No new physical or mathematical entities are introduced.

free parameters (1)
  • Vigenère key (fixed policy) = not disclosed (pre-registered per run)
    Chosen by hand and fixed before evaluation; included in the prompt, so it provides no secrecy. Success rates could in principle depend on the key, but no key search was performed. The paper states the key policy is pre-registered and not per-prompt tuned.
axioms (3)
  • standard math Vigenère and ROT13 are reversible for ASCII letters with case preservation, and the parity partition with ORDER=0-even has a unique inverse.
    Section 4.2 defines the transformations and the inverse procedure; reversibility is stated as a property of the encoder/parser, not accompanied by a formal proof.
  • domain assumption The target LLM can parse and follow the wrapper's multi-step instructions (reverse ROT13, parse fields, decrypt, interleave, execute).
    Section 4.1 assumes instruction-tuned models can perform these text transformations; the empirical results are the test of this assumption.
  • domain assumption The Llama-3.3-70B automated judge labels reconstruction and execution accurately, and the authors' 300-sample audit is a valid reliability check.
    Section 5.2 relies on the judge's binary decisions to compute all reported rates; an incorrect judge would directly affect the headline numbers.

pith-pipeline@v1.3.0-daily-deepseek · 15639 in / 9129 out tokens · 86099 ms · 2026-08-01T08:32:07.855714+00:00 · methodology

0 comments
read the original abstract

Large language models (LLMs) are becoming increasingly integrated into mainstream development platforms and daily technological workflows, typically behind moderation and safety controls. Despite these controls, preventing prompt-based policy evasion remains challenging, and adversaries continue to "jailbreak" LLMs by crafting prompts that circumvent implemented safety mechanisms. Prior work has established cipher-mediated interaction, code-embedded decryption, prompt decomposition and reconstruction, and layered custom encryption as viable attack primitives. However, reported evaluations generally collapse visible acceptance, successful recovery of the concealed request, and subsequent execution into an aggregate attack-success outcome. This leaves limited evidence about where multistage prompt-transformation attacks fail within an observable black-box interaction. This paper introduces RoguePrompt, a jailbreak pipeline that partitions a forbidden prompt and applies two nested encodings, Vigenere followed by ROT13, along with natural-language reconstruction instructions. RoguePrompt was developed and evaluated under a black-box threat model, with only API or user-interface access to the hosted models, and was tested on 313 real-world, hard-rejected prompts. Success was measured in terms of moderation bypass, instruction reconstruction, and execution when the relevant stage exceeded its automated criterion. RoguePrompt achieved average rates of 93.93% for filter bypass, 79.02% for reconstruction, and 70.18% for execution. These results demonstrate the effectiveness of layered prompt encoding while providing stage-level evidence of where multistage jailbreaks fail during moderation bypass, instruction reconstruction, and execution.

Figures

Figures reproduced from arXiv: 2607.27373 by Benyamin Tafreshian, Prathamesh Dhake.

Figure 1
Figure 1. Figure 1: Self-reconstruction jailbreak: blocked request [PITH_FULL_IMAGE:figures/full_fig_p001_1.png] view at source ↗
Figure 2
Figure 2. Figure 2: Stage-wise @3 success rates by method and tested model configuration ( [PITH_FULL_IMAGE:figures/full_fig_p008_2.png] view at source ↗

discussion (0)

Sign in with ORCID, Apple, or X to comment. Anyone can read and Pith papers without signing in.

Reference graph

Works this paper leans on

40 extracted references · 1 canonical work pages

  1. [1]

    Anthropic. 2024. Model Card and Evaluations for Claude Models. https://www- cdn.anthropic.com/c6a80a657af445f40e31afac050f3bf76d3b1404.pdf Claude 3 model card / safety overview (PDF)

  2. [2]

    Yuntao Bai, Saurav Kadavath, Sandipan Kundu, et al. 2022. Constitutional AI: Harmlessness from AI Feedback. arXiv preprint arXiv:2212.08073

  3. [3]

    Miles Brundage, Shahar Avin, Jack Clark, et al . 2018. The Malicious Use of Artificial Intelligence: Forecasting, Prevention, and Mitigation. arXiv preprint arXiv:1802.07228

  4. [4]

    Sizhe Chen, Julien Piet, Chawin Sitawarin, and David Wagner. 2025. StruQ: Defending Against Prompt Injection with Structured Queries. In34th USENIX Security Symposium (USENIX Security 25). USENIX Association, Berkeley, CA, USA, 2383–2400. https://www.usenix.org/conference/usenixsecurity25/present ation/chen-sizhe

  5. [5]

    Edoardo Debenedetti, Jie Zhang, Mislav Balunović, Luca Beurer-Kellner, Marc Fischer, and Florian Tramèr. 2024. AgentDojo: A Dynamic Environment to Evaluate Prompt Injection Attacks and Defenses for LLM Agents. doi:10.5555/37 37916.3740552 Advances in Neural Information Processing Systems (NeurIPS

  6. [6]

    Gelei Deng, Yi Liu, Yuekang Li, et al. 2024. MASTERKEY: Automated Jailbreaking of Large Language Model Chatbots. doi:10.14722/ndss.2024.24188 Network and Distributed System Security (NDSS) Symposium 2024

  7. [7]

    Samuel Gehman, Suchin Gururangan, Maarten Sap, Yejin Choi, and Noah A. Smith. 2020. RealToxicityPrompts: Evaluating Neural Toxic Degeneration in Language Models. InFindings of the Association for Computational Linguistics: EMNLP 2020. Association for Computational Linguistics, Stroudsburg, PA, USA, 3356–3369. doi:10.18653/v1/2020.findings-emnlp.301

  8. [8]

    Google DeepMind. 2022. Building safer dialogue agents. https://deepmind.goo gle/blog/building-safer-dialogue-agents/ Blog post introducing the Sparrow dialogue agent

  9. [9]

    Competency

    Divij Handa, Zehua Zhang, Amir Saeidi, Shrinidhi Kumbhar, Md Nayem Uddin, Aswin RRV, and Chitta Baral. 2025. When “Competency” in Reasoning Opens the Door to Vulnerability: Jailbreaking LLMs via Novel Complex Ciphers. doi:10 .48550/arXiv.2402.10601 Reliable ML from Unreliable Data Workshop at NeurIPS 2025; arXiv:2402.10601

  10. [10]

    Homa Hosseini, Sreeram Kannan, Baosen Zhang, and Radha Poovendran. 2017. Deceiving Google’s Perspective API Built for Detecting Toxic Comments. arXiv preprint arXiv:1702.08138

  11. [11]

    Bo Hui, Haolin Yuan, Neil Gong, Philippe Burlina, and Yinzhi Cao. 2024. PLeak: Prompt Leaking Attacks against Large Language Model Applications. InPro- ceedings of the 2024 ACM SIGSAC Conference on Computer and Communications Security (CCS). Association for Computing Machinery, New York, NY, USA, 3600–3614. doi:10.1145/3658644.3670370

  12. [12]

    Daniel Kang, Xuechen Li, Ion Stoica, Carlos Guestrin, Matei Zaharia, and Tat- sunori Hashimoto. 2023. Exploiting Programmatic Behavior of LLMs: Dual-Use Through Standard Security Attacks. arXiv preprint arXiv:2302.05733

  13. [13]

    2012.The Menlo Report: Ethical Principles Guiding Information and Communication Technology Research

    Erin Kenneally and David Dittrich. 2012.The Menlo Report: Ethical Principles Guiding Information and Communication Technology Research. Technical Report. U.S. Department of Homeland Security, Science and Technology Directorate, Cyber Security Division

  14. [14]

    Auguste Kerckhoffs. 1883. La cryptographie militaire.Journal des sciences militaires9 (1883), 5–38, 161–191. Published in two parts (Jan. 1883, pp. 5–38; Feb. 1883, pp. 161–191)

  15. [15]

    Torsten Krauß, Hamid Dashtbani, and Alexandra Dmitrienko. 2025. TwinBreak: Jailbreaking LLM Security Alignments based on Twin Prompts. InProceedings of the 34th USENIX Security Symposium (USENIX Security 2025). USENIX Associa- tion, Berkeley, CA, USA, 2343–2362. doi:10.5555/3766078.3766199

  16. [16]

    Xirui Li, Ruochen Wang, Minhao Cheng, Tianyi Zhou, and Cho-Jui Hsieh. 2024. DrAttack: Prompt Decomposition and Reconstruction Makes Powerful LLMs Jailbreakers. InFindings of the Association for Computational Linguistics: EMNLP

  17. [17]

    Yi Liu, Gelei Deng, Yuekang Li, et al . 2025. Prompt Injection attack against LLM-integrated Applications. arXiv preprint arXiv:2306.05499

  18. [18]

    doi:10.18653/v1/2024.findings-emnlp.813

    Association for Computational Linguistics, Miami, Florida, USA, 13891– 13913. doi:10.18653/v1/2024.findings-emnlp.813

  19. [19]

    Huijie Lv, Xiao Wang, Yuansen Zhang, Caishuang Huang, Shihan Dou, Junjie Ye, Tao Gui, Qi Zhang, and Xuanjing Huang. 2024. CodeChameleon: Personalized Encryption Framework for Jailbreaking Large Language Models. doi:10.48550/a rXiv.2402.16717 arXiv preprint arXiv:2402.16717

  20. [20]

    Yi Liu, Gelei Deng, Zhengzi Xu, et al. 2024. Jailbreaking ChatGPT via Prompt Engineering: An Empirical Study. arXiv preprint arXiv:2305.13860

  21. [21]

    OpenAI. 2023. GPT-4 System Card. https://cdn.openai.com/papers/gpt-4- system-card.pdf Technical report

  22. [22]

    Meta. 2024. Llama 3.3 Model Card. https://www.llama.com/docs/model-cards- and-prompt-formats/llama3_3/ Model card for Llama-3.3-70B-Instruct

  23. [23]

    Ethan Perez, Saffron Huang, Francis Song, Trevor Cai, Roman Ring, John Aslanides, Amelia Glaese, Nat McAleese, and Geoffrey Irving. 2022. Red Teaming Language Models with Language Models. InProceedings of the 2022 Confer- ence on Empirical Methods in Natural Language Processing (EMNLP). Association for Computational Linguistics, Abu Dhabi, United Arab Emi...

  24. [24]

    Long Ouyang, Jeffrey Wu, Xu Jiang, et al. 2022. Training Language Models to Follow Instructions with Human Feedback. InAdvances in Neural Information Processing Systems 35, Vol. 35. Curran Associates, Inc., Red Hook, NY, USA, 27730–27744. doi:10.48550/arXiv.2203.02155

  25. [25]

    Zedian Shao, Hongbin Liu, Jaden Mu, and Neil Zhenqiang Gong. 2025. Enhancing Prompt Injection Attacks to LLMs via Poisoning Alignment. InProceedings of the 2025 Workshop on Artificial Intelligence and Security (AISec ’25). Association for Computing Machinery, New York, NY, USA, 13–27. doi:10.1145/3733799.3762963

  26. [26]

    2000.Secrets and Lies: Digital Security in a Networked World

    Bruce Schneier. 2000.Secrets and Lies: Digital Security in a Networked World. John Wiley & Sons, New York, NY

  27. [27]

    Alexandra Souly, Qingyuan Lu, Dillon Bowen, et al. 2024. A StrongREJECT for Empty Jailbreaks. arXiv preprint arXiv:2402.10260. RoguePrompt

  28. [28]

    Minkyoo Song, Hanna Kim, Jaehan Kim, Seungwon Shin, and Sooel Son. 2025. Refusal Is Not an Option: Unlearning Safety Alignment of Large Language Models. InProceedings of the 34th USENIX Security Symposium (USENIX Security 2025). USENIX Association, Berkeley, CA, USA, 319–338. doi:10.5555/3766078.3766095

  29. [29]

    Laura Weidinger, Jonathan Uesato, Maribeth Rauh, et al. 2022. Taxonomy of Risks Posed by Language Models. InProceedings of the 2022 ACM Conference on Fairness, Accountability, and Transparency (FAccT ’22). Association for Computing Machinery, New York, NY, USA, 214–229. doi:10.1145/3531146.3533088

  30. [30]

    Saba Sturua, Isabelle Mohr, Mohammad Kalim Akram, Michael Günther, Bo Wang, Markus Krimmel, Feng Wang, Georgios Mastrapas, Andreas Koukounas, Nan Wang, and Han Xiao. 2024. jina-embeddings-v3: Multilingual Embeddings With Task LoRA. doi:10.48550/arXiv.2409.10173 arXiv preprint arXiv:2409.10173

  31. [31]

    Youliang Yuan, Wenxiang Jiao, Wenxuan Wang, Jen-tse Huang, Pinjia He, Shum- ing Shi, and Zhaopeng Tu. 2024. GPT-4 Is Too Smart To Be Safe: Stealthy Chat with LLMs via Cipher. https://openreview.net/forum?id=MbfAK4s61A The Twelfth International Conference on Learning Representations (ICLR 2024)

  32. [32]

    Jiahao Yu, Haozheng Luo, Jerry Yao-Chieh Hu, Yan Chen, Wenbo Guo, Han Liu, and Xinyu Xing. 2025. Mind the Inconspicuous: Revealing the Hidden Weakness in Aligned LLMs’ Refusal Boundaries. InProceedings of the 34th USENIX Security Symposium (USENIX Security 2025). USENIX Association, Berkeley, CA, USA, 259–278

  33. [33]

    Qiusi Zhan, Zhixiang Liang, Zifan Ying, and Daniel Kang. 2024. InjecAgent: Benchmarking Indirect Prompt Injections in Tool-Integrated Large Language Model Agents. arXiv preprint arXiv:2403.02691

  34. [34]

    Yi Zeng, Hongpeng Lin, Jingwen Zhang, Diyi Yang, Ruoxi Jia, and Weiyan Shi

  35. [35]

    arXiv preprint arXiv:2401.06373

    How Johnny Can Persuade LLMs to Jailbreak Them: Rethinking Persuasion to Challenge AI Safety by Humanizing LLMs. arXiv preprint arXiv:2401.06373

  36. [36]

    Wei Zhou, Xiaogang Zhu, Qing-Long Han, Lin Li, Xiao Chen, Sheng Wen, and Yang Xiang. 2025. The Security of Using Large Language Models: A Survey With Emphasis on ChatGPT.IEEE/CAA Journal of Automatica Sinica12, 1 (2025), 1–26. doi:10.1109/JAS.2024.124983 Benyamin Tafreshian and Prathamesh Dhake Usage of Generative AI The authors designed the methodology a...

  37. [37]

    Yi Zhang, Kai Chen, Yuekang Li, Gelei Deng, Kailong Wang, Tianwei Zhang, and Yang Liu. 2024. Goal-Driven Generative Prompt Injection Attack on Large Language Models. arXiv preprint arXiv:2404.07234

  38. [38]

    Zhuo Zhang, Guangyu Shen, Guanhong Tao, Siyuan Cheng, and Xiangyu Zhang

  39. [39]

    In2024 IEEE Symposium on Security and Privacy (SP)

    On Large Language Models’ Resilience to Coercive Interrogation. In2024 IEEE Symposium on Security and Privacy (SP). IEEE, Los Alamitos, CA, USA, 826–844. doi:10.1109/SP54263.2024.00208

  40. [2024]

    Datasets and Benchmarks Track