BlogLLM Benchmark Scores as Published, Side by Side

B3 AI Security Benchmark: Results as Published

Every result the catalog holds for B3 AI Security Benchmark: 6 models from 4 developers, read from 1 page. Each number is as printed by the company named beside it; nothing is ranked or rescored. Models are listed by developer, newest first.

Area Safety and AlignmentMaintainer Lakera AI (Julia Bazinska, Max Mathys, and co-authors)Introduced 2025Data version 2026103001, as of 2026-10-30

The b3 benchmark, Breaking Agent Backbones, tests whether the language model inside an agent gives in to realistic prompt-injection attacks. The attacks were crowdsourced, 194,331 unique attempts in all, and then placed into threat snapshots: frozen states of 10 agent applications, each tried at three defense levels. The paper scores the main set of 210 attacks by repeating each one and applying that snapshot's own checker. The published figure is a vulnerability score, the average of those checker scores, and a lower score means the model was harder to break.

B3 AI Security Benchmark (attack resistance)

ModelValuePrinted bySetup as printed
DeepSeek-V4-Pro-0813DeepSeek85.2%Mistral AI, Mistral Large 4 (preview)checked 2026-10-15-
Kimi K3Moonshot AI, released 2026-07-1688.1%Mistral AI, Mistral Large 4 (preview)checked 2026-10-15-
Kimi K2.6Moonshot AI, released 2026-04-2083.8%Mistral AI, Mistral Large 4 (preview)checked 2026-10-15-
GLM-5.3Z.ai, released 2026-08-1893.3%Mistral AI, Mistral Large 4 (preview)checked 2026-10-15-
GLM-5.2Z.ai, released 2026-06-1688.1%Mistral AI, Mistral Large 4 (preview)checked 2026-10-15-
Mistral Large 4 (preview)Mistral AI, released 2026-10-0693.3%Mistral AI, Mistral Large 4 (preview)checked 2026-10-15-

Every number here is read from the same catalog file as the benchmark table, data version 2026103001, and is the number the table shows for that model and test. Where one page printed a model under several setups, each value is listed. The catalog is public in armanobosyan/sugra-llm-benchmarks; a wrong number can be reported from the table, with Report an error under the value, or as an issue in that repository.