Evaluation lab · San Francisco · London · Zürich
Reinforced Labs Request a briefing
Research note

Attack success rate is a curve, not a number: power laws for Best-of-N jailbreaks

An attack success rate means little without the attacker's budget. Resampling attacks keep improving with more attempts, and the aggregate curve often follows a power law whose exponent is set by how many prompts are nearly unbreakable. We derive it, test extrapolation, and show how single-budget comparisons misrank defences.

An attack success rate (ASR) is only meaningful next to the attacker's budget. Resampling attacks such as Best-of-N jailbreaking keep improving as the budget grows, and the aggregate curve often follows a power law. This note derives where that power law comes from, tests two ways of extrapolating ASR from a small budget to a large one, shows how a single-budget comparison can rank two defences the wrong way round, and covers intervals for rare successes. Every number comes from a seeded simulation, labelled as such.

A concrete example: 159 prompts, 100 attempts each#

A red team takes 159 harmful requests and, for each one, generates up to 100 randomly perturbed variants (shuffled characters, random capitalisation, small typos), stopping when a variant gets a harmful answer. This is the shape of Best-of-N (BoN) jailbreaking, introduced by Hughes and colleagues, which reached 89% ASR on GPT-4o and 78% on Claude 3.5 Sonnet with 10,000 augmented samples per request [1]. In our simulation the team sees 3% of requests succeed on the first attempt, 30% within 10, and 67% within 100.

The deployment question is about larger budgets. Sending 10,000 automatically generated variants costs a motivated attacker little. Will ASR at 10,000 be 75%, 90% or 99%? Running 10,000 attempts on every prompt for every model version and every defence configuration is expensive, so teams want to extrapolate. Hughes and colleagues observed that falls as a power law in over several orders of magnitude [1], and Schaeffer and colleagues explained why [2]. That explanation also tells you when the extrapolation breaks.

Where the power law comes from#

Each prompt is exponential#

Let prompt have a per-attempt success probability under the attack's random augmentations. If attempts are independent draws, the probability that at least one of attempts succeeds is

where is the number of attempts. The failure probability for a single prompt decays exponentially: after about attempts, the prompt is probably broken. Brown and colleagues studied the same repeated-sampling structure on reasoning and coding problems, where coverage keeps rising with the number of samples [3].

The aggregate is polynomial#

The reported number averages over prompts:

where is the number of prompts. If the are spread across many orders of magnitude, each value of breaks a new slice of prompts: those with near . How fast the aggregate rises therefore depends on how much mass the distribution of has near zero. Model that distribution as , with density proportional to . The expected failure rate has a closed form:

where is the beta function and the gamma function. The approximation uses . Once ASR is close to 1, , so

In words: the power-law exponent is the shape of the per-prompt difficulty distribution near zero. A small means many prompts that almost never break, and a slow climb. This is the distributional account of Schaeffer and colleagues [2], who also showed that estimating the distribution directly forecasts the exponent with much less compute than fitting the curve.

Simulation setup. 159 prompts with : a mean per-attempt rate of 5.5%, a median of about 2%, and 17% of prompts below one success in a thousand attempts. Attempts are independent Bernoulli draws. Over the observed range the fitted exponent is , not the asymptotic 0.35, because the approximation only holds once ASR is near 1. That gap is one reason power-law fits drift.

Extrapolating from a small budget#

We compared two estimators of ASR at from a budget of 30, 100 or 300 attempts per prompt, over 500 simulated red-team runs each. The power-law method fits a line to against and extrapolates. The distributional method fits by maximum likelihood to the per-prompt success counts (a beta-binomial model) and evaluates the closed form above. Both use the same attempts.

Budget per promptPower law: median abs. errorPower law: median biasBeta-binomial: median abs. errorBeta-binomial: median bias
301.7 pts+0.2 pts2.0 pts+0.3 pts
1001.4 pts+0.9 pts1.4 pts-0.1 pts
3001.4 pts+1.0 pts1.2 pts0.0 pts

The true expected ASR at 10,000 averaged 93%. When the population really is Beta-distributed, both methods work: errors of one to two points from budgets 30 to 300 times smaller than the target. The power-law fit carries a small upward bias that does not shrink with budget, because it fits the pre-asymptotic exponent. The beta-binomial fit is unbiased here, which is unsurprising: the simulation draws from the model it assumes.

0%25%50%75%100%1101001,00010,000Attempts per prompt N (log scale)Attack success rateextrapolatedceiling 79% (breakable prompts)Heavy-tailed prompts: observed power-law fit on N ≤ 10025% unbreakable: observed power-law fit on N ≤ 100
Figure 1. Two simulated red-team runs on 159 prompts, power law fitted on (dashed) and extrapolated into the shaded region. Green: Beta-distributed prompts; the fit predicts 95% at 10,000 against an observed 91%. Red: the same population with 25% of prompts unbreakable by this attack family; the fit predicts 83% against an observed 72%, and the true ceiling is 79%.

A worked example: the budget for a target ASR#

Inverting the fitted law gives the attacker budget needed to reach a target success rate :

where and are the fitted constants. For the green run in Figure 1, fitted on 100 attempts per prompt, and . Reaching 90% needs attempts per prompt. Reaching 99% needs in the denominator, and . Each extra "nine" of ASR multiplies the budget by roughly , about 125 here. The exponent, not the intercept, decides how expensive the last prompts are.

The defender reads the same equation the other way. If the threat model is an attacker with a budget of 10,000 automated attempts per request, the quantity to report is ASR at 10,000, and the useful engineering target is the exponent: a defence that halves does more against a patient attacker than one that halves ASR at a single attempt. That is also why the extrapolation's assumptions matter so much: an error in of 0.05 changes the 99% budget by a factor of about three.

When the tail stops#

The extrapolation assumes the distribution of continues smoothly towards zero. Real prompt sets break that assumption. Some requests are refused because of a filter the augmentation never gets past, some are effectively impossible because the "harmful" completion is not something the model knows, and some defences block a whole category deterministically. Each creates a mass of prompts with , which puts a ceiling below 100% on ASR at any budget.

In the red run of Figure 1, 25% of prompts are unbreakable. At budget 100, the power law predicts 83% at 10,000, and the beta-binomial predicts 81%, against an expected 72%. Neither can tell a prompt with from one with after 100 failures, so both treat the unbreakable prompts as merely hard. The fix is not a cleverer curve. It is to run a subset of prompts to a much larger budget, look for a plateau directly, and report the forecast as conditional on the tail continuing. Jones and colleagues took the complementary route for deployment-scale risks, forecasting the largest elicitation probabilities across up to three orders of magnitude more queries than were tested [4].

Comparing defences fairly#

Suppose two defences are measured at one attempt per prompt. Defence A has an ASR of 1.3%; defence B has 2.8%. A looks twice as strong. Now let the attacker resample.

0%25%50%75%100%1101001,00010,000Attacker budget N (log scale)Attack success ratecurves cross at N = 20Defence A: ASR@1 = 1.3%Defence B: ASR@1 = 2.8%
Figure 2. Simulated ASR against budget for two defences, 4,000 prompts each. A's prompts are uniformly moderately hard, ; B lets more through on the first try but leaves a heavy tail of prompts that almost never break, . The curves cross at 20 attempts. At 1,000 attempts A is at 98% and B at 56%.

A defence that lowers every prompt's success probability a little looks good at and collapses under resampling, because goes to 1 for every . A defence that makes a subset of prompts near-impossible looks worse at and holds up. Ranked by attempts needed to reach 50% ASR, A falls at 63 and B at 501. Single-budget comparisons hide this. Rules for comparing:

  1. Compare full curves on a log-budget axis, or at least at the budget your threat model assumes, not at .
  2. Use the same prompts and the same augmentation seeds for both defences, so the comparison is paired and differences in prompt mix cannot masquerade as differences in defence.
  3. Hold attacker compute fixed, not attempts, when attacks differ in cost per attempt. An optimised suffix attack [5] and a resampling attack are not comparable per attempt.
  4. Use adaptive attacks. Andriushchenko and colleagues reported 100% ASR against a long list of safety-aligned models using simple adaptive methods, with the template and method tuned to each target [6]; a defence evaluated only against a static corpus has not been tested against what it will meet.
  5. Standardise the judge. HarmBench [7] and JailbreakBench [8] exist partly because ASR moves by large amounts depending on which classifier decides that an output is harmful.

Large defence evaluations now report effort as well as outcomes. The Constitutional Classifiers work, for example, reported over 3,000 estimated hours of human red teaming alongside its automated evaluations [9]. Effort is the denominator that makes an ASR interpretable.

Confidence intervals for rare successes#

At small budgets, or against strong defences, successes are rare and the textbook interval fails. With successes in trials, the Wald interval collapses to when . The Wilson interval [10] inverts the score test instead:

where and is the normal quantile (1.645 for a 90% interval). It stays sensible at , giving an upper limit of about . The Clopper-Pearson interval [11] inverts the exact binomial test and is conservative. For zero successes, the rule of three [12] gives a quick 95% upper bound of : no successes in 3,000 attempts bounds the per-attempt rate below about .

We checked coverage of nominal 90% intervals with attempts, 20,000 simulated experiments per row:

True per-attempt rateRuns with zero successesWaldWilsonClopper-Pearson
0.05%61%39%91%99%
0.2%14%86%95%98%
1%0%91%92%92%

Attempts are clustered in prompts#

There is a second, larger trap. Attempts on the same prompt share that prompt's , so 5,000 attempts spread over 100 prompts are not 5,000 independent trials. We simulated 100 prompts with 50 attempts each, , and estimated the mean per-attempt rate. A Wilson interval that treats all 5,000 attempts as independent covered the true mean 77% of the time at nominal 90%. A bootstrap that resamples prompts, not attempts, covered 87%: closer, though still short with only 100 heavy-tailed clusters. Report the number of prompts as your sample size, resample prompts, and see our note on clustered standard errors for the analytic version.

01020301e-61e-41e-21e0per-attempt pprompts0%25%50%75%100%1101001k10kattempts NASRbudget 100
100 0.35 0%

Figure 3 (interactive). Left: the distribution of per-attempt success probabilities across 159 simulated prompts, on a log axis. Right: observed ASR up to the budget (dots), the power law fitted to those points and extrapolated to 10,000 (green), and the exact expected curve for these prompts (dashed). Lower fattens the tail near zero and flattens the curve; a nonzero unbreakable share adds a ceiling the fit cannot see.

Practice: reporting ASR#

QuestionReport
How strong is the attack?ASR at several budgets on a log scale, with the attacker's cost per attempt
What happens at deployment-scale budgets?An extrapolation with its assumption stated, plus a deep run on a subset to check for a plateau
Is defence A better than B?Paired curves on the same prompts and seeds, at the threat-model budget
How uncertain is the ASR?A prompt-level bootstrap interval; Wilson or Clopper-Pearson per prompt when successes are rare
What does zero successes mean?An upper bound (about at 95%), never "0%"
Which judge decided "harmful"?The classifier and its measured error rate on a labelled sample

The core of both estimators, as used in the simulation:

import numpy as np
from scipy import optimize, special

def powerlaw_extrapolate(n_grid, asr, n_target):
    ok = (asr > 0) & (asr < 1)
    k, logc = np.polyfit(np.log(n_grid[ok]), np.log(-np.log(asr[ok])), 1)
    return np.exp(-np.exp(logc) * n_target ** k)     # k is negative here

def betabinomial_extrapolate(successes, budget, n_target):
    def nll(log_ab):
        a, b = np.exp(log_ab)
        return -(special.betaln(successes + a, budget - successes + b) - special.betaln(a, b)).sum()
    a, b = np.exp(optimize.minimize(nll, np.log([0.5, 5.0]), method="Nelder-Mead").x)
    return 1 - np.exp(special.betaln(a, b + n_target) - special.betaln(a, b))

Failure modes#

Correlated attempts. The exponential per-prompt model assumes independent attempts. Augmentations drawn from a narrow family (only capitalisation, say) produce correlated attempts, and per-prompt failure decays more slowly than predicts.

Judge false positives compound with budget. If the harm classifier flags a benign output as harmful with probability , a prompt that is never truly broken still "succeeds" within attempts with probability . At and , that is essentially certain. ASR at large budgets is only as good as the judge's false-positive rate, so successes at large budgets need human or second-judge confirmation.

Severity is not binary. A curve of "any harmful answer" mixes a vague hint with a complete procedure. Track ASR per severity tier; the high-severity curve is usually the one with the heavy tail.

Attacker capability changes the curve. Panfilov and colleagues found that attack success with LLM-based attackers depends on the capability gap between attacker and target [13]. Power-law fits from one attacker do not transfer to a stronger one.

Multi-turn and stateful attacks. Resampling a single message is the simplest budget to count. Multi-turn attacks spend their budget on conversation length and branching, and an attacker who learns from each refusal is no longer drawing independent attempts. The per-prompt exponential model then understates success at a given budget, sometimes badly. Count budget in the unit the attacker actually pays for, such as model calls or tokens, and treat curves from adaptive attackers as a separate family rather than extending a resampling curve.

Prompt set drift. The exponent is a property of the prompt distribution. Adding easy prompts raises ASR at every budget and changes the fitted exponent; compare curves only on fixed prompt sets.

The useful mental model is the one in the derivation: every prompt falls exponentially, and the population's curve is a readout of how many prompts sit near zero. Measure that distribution, check whether it has a floor, and the large-budget number stops being a guess.

Frequently asked questions#

Why does Best-of-N jailbreak success follow a power law?

Each prompt's chance of surviving N attempts falls exponentially, but prompts differ enormously in difficulty. When many prompts have per-attempt success rates near zero, the average over prompts falls polynomially, and the exponent equals the shape of the difficulty distribution near zero.

Can I extrapolate attack success rate from 100 attempts to 10,000?

In our simulation, both a power-law fit and a beta-binomial fit landed within about 1.5 points when prompt difficulties followed a smooth distribution. When 25% of prompts were unbreakable, both overpredicted by about 10 points, so check a subset at a large budget for a plateau.

How should I compare two jailbreak defences?

Compare full ASR curves against attacker budget on the same prompts and augmentation seeds. A defence that lowers every prompt's success rate slightly can win at one attempt and lose badly at a thousand, as in our simulated example where the curves crossed at 20 attempts.

What confidence interval should I use when I observe zero successful attacks?

Use a Wilson or Clopper-Pearson interval, or the rule of three for a quick 95% upper bound of 3 divided by the number of attempts. The Wald interval collapses to zero and covered the true rate only 39% of the time in our simulation at a 0.05% rate.

Is the number of attempts the right sample size for ASR?

No. Attempts on the same prompt share that prompt's difficulty, so the number of prompts is the effective sample size. Treating 5,000 attempts on 100 prompts as independent gave 77% coverage at a nominal 90% in our simulation.

Sources#

  1. J. Hughes, S. Price, A. Lynch, R. Schaeffer et al.. Best-of-N Jailbreaking, 2024. arxiv.org
  2. R. Schaeffer, J. Kazdan, J. Hughes, J. Juravsky et al.. How Do Large Language Monkeys Get Their Power (Laws)?, 2025. arxiv.org
  3. B. Brown, J. Juravsky, R. Ehrlich, R. Clark et al.. Large Language Monkeys: Scaling Inference Compute with Repeated Sampling, 2024. arxiv.org
  4. E. Jones, M. Tong, J. Mu, M. Mahfoud et al.. Forecasting Rare Language Model Behaviors, 2025. arxiv.org
  5. A. Zou, Z. Wang, N. Carlini, M. Nasr et al.. Universal and Transferable Adversarial Attacks on Aligned Language Models, 2023. arxiv.org
  6. M. Andriushchenko, F. Croce, N. Flammarion. Jailbreaking Leading Safety-Aligned LLMs with Simple Adaptive Attacks, 2024. arxiv.org
  7. M. Mazeika, L. Phan, X. Yin, A. Zou et al.. HarmBench: A Standardized Evaluation Framework for Automated Red Teaming and Robust Refusal, 2024. arxiv.org
  8. P. Chao, E. Debenedetti, A. Robey, M. Andriushchenko et al.. JailbreakBench: An Open Robustness Benchmark for Jailbreaking Large Language Models, 2024. arxiv.org
  9. M. Sharma, M. Tong, J. Mu, J. Wei et al.. Constitutional Classifiers: Defending against Universal Jailbreaks across Thousands of Hours of Red Teaming, 2025. arxiv.org
  10. E. B. Wilson. Probable Inference, the Law of Succession, and Statistical Inference, 1927. doi.org
  11. C. J. Clopper, E. S. Pearson. The Use of Confidence or Fiducial Limits Illustrated in the Case of the Binomial, 1934. doi.org
  12. J. A. Hanley, A. Lippman-Hand. If Nothing Goes Wrong, Is Everything All Right? Interpreting Zero Numerators, 1983. doi.org
  13. A. Panfilov, P. Kassianik, M. Andriushchenko, J. Geiping. Capability-Based Scaling Trends for LLM-Based Red-Teaming, 2025. arxiv.org

Know the number before you ship.

A 45-minute working session with an evaluation engineer. Bring one use case; leave with a threat model, a draft eval plan with sample sizes, and an honest read on where you stand.