Skip to content
OpenTrain AIFor AI Companies

HFEPX · Eval paper review

Beyond Attack Success Rate: Cost-Aware Metric for Evaluating Iterative LLM Jailbreaks

Rohan Menon, Chih-Hong Cheng

Published

Oct 19, 2026

Citations

0

Trust level

High

Usefulness score

65/100 (Medium)

Extraction confidence

80% (High)

Derived from extracted protocol signals and abstract evidence.

Rater population

Not reported

Signals refreshed

Oct 22, 2026

Should you rely on this paper?

This paper has useful evaluation signal, but protocol completeness is partial; pair it with related papers before deciding implementation strategy.

Use this as a practical starting point for protocol research, then validate against the original paper.

Best use

Secondary protocol comparison source

Use if you need

A benchmark-and-metrics comparison anchor.

What to verify

Validate the evaluation procedure and quality controls in the full paper before operational use.

Main weakness

No major weakness surfaced.

Human feedback signal
Detected
From extracted signals
Evaluation signal
Detected
Eval setup described
Usefulness for eval research
65/100
Moderate-confidence candidate

Useful as a secondary reference; validate protocol details against neighboring papers.

Abstract

Attack success rate (ASR) evaluates jailbreaks against large language models without accounting for repeated calls to the victim model. Yet each additional call gives the deployed system another opportunity to detect the attack and intervene. We introduce $\mathrm{ASR}_{\mathrm{STEP}}$, which penalizes additional victim-model calls while retaining binary success judgments. Our evaluation considers GCG, PAIR with a step budget, and a single-step PAP baseline on JailBreakBench across three model families. GCG's scores decrease by 7.0-8.7 percentage points after discounting, while PAP's remain unchanged. While for PAIR attack, we see a wider discounting range between 3.4-12 percentage points, showing that the "step" quantity differs per iterative strategy. Reporting both metrics makes the discount due to repeated victim-model interaction explicit. Code is available here: https://github.com/SuELS-Group/beyond_asr.

What we could verify

These are the protocol signals we could actually recover from the available paper metadata. Use them to decide whether this paper is worth deeper reading.

Human Feedback Types

strong

Red Team

Directly usable for protocol triage.

"Attack success rate (ASR) evaluates jailbreaks against large language models without accounting for repeated calls to the victim model."

Evaluation Modes

strong

Automatic Metrics

Includes extracted eval setup.

"Attack success rate (ASR) evaluates jailbreaks against large language models without accounting for repeated calls to the victim model."

Quality Controls

missing

Not reported

No explicit QC controls found.

"Attack success rate (ASR) evaluates jailbreaks against large language models without accounting for repeated calls to the victim model."

Benchmarks / Datasets

strong

Jailbreakbench

Useful for quick benchmark comparison.

"Our evaluation considers GCG, PAIR with a step budget, and a single-step PAP baseline on JailBreakBench across three model families."

Reported Metrics

strong

Success rate, Jailbreak success rate

Useful for evaluation criteria comparison.

"Attack success rate (ASR) evaluates jailbreaks against large language models without accounting for repeated calls to the victim model."

Benchmarks and datasets

Jailbreakbench

Reported metrics

success ratejailbreak success rate
Human feedback details
Uses human feedback
Yes
Feedback types
Red Team
Rater population
Not reported
Expertise required
Math, Coding
Evaluation details
Evaluation modes
Automatic Metrics
Agentic eval
None
Quality controls
Not reported
Evidence quality
High
Use this page as
Secondary protocol comparison source

Research brief

Metadata summary

Attack success rate (ASR) evaluates jailbreaks against large language models without accounting for repeated calls to the victim model.

Based on abstract + metadata only. Check the source paper before making high-confidence protocol decisions.

Key takeaways

  • Attack success rate (ASR) evaluates jailbreaks against large language models without accounting for repeated calls to the victim model.
  • Yet each additional call gives the deployed system another opportunity to detect the attack and intervene.
  • We introduce $\mathrm{ASR}_{\mathrm{STEP}}$, which penalizes additional victim-model calls while retaining binary success judgments.

Researcher actions

  • Compare this paper against nearby papers in the same arXiv category before using it for protocol decisions.
  • Check the full text for explicit evaluation design choices (raters, protocol, and metrics).
  • Use related-paper links to find stronger protocol-specific references.

Caveats

  • Generated from abstract + metadata only; no PDF parsing.
  • Signals below are heuristic and may miss details reported outside the abstract.

Recommended queries

Contribution summary

  • We introduce ASR_{STEP}, which penalizes additional victim-model calls while retaining binary success judgments.
  • Our evaluation considers GCG, PAIR with a step budget, and a single-step PAP baseline on JailBreakBench across three model families.

Why it matters for eval

  • Our evaluation considers GCG, PAIR with a step budget, and a single-step PAP baseline on JailBreakBench across three model families.

Researcher checklist

  • Human feedback protocol is explicit

    Detected: Red Team

  • Evaluation mode is explicit

    Detected: Automatic Metrics

  • Quality control reporting appears

    No calibration/adjudication/IAA control explicitly detected.

  • Benchmark or dataset anchors are present

    Detected: Jailbreakbench

  • Metric reporting is present

    Detected: success rate, jailbreak success rate