RedCode
Models meet adversarial prompts to generate or run harmful code. Generation is model-judged and execution is checked in a container.
Over 4,000 test cases in two parts. RedCode-Exec has 4,050 instances over 25 vulnerability types in Python, Bash and natural language, run in a Docker sandbox. RedCode-Gen has 160 prompts with function signatures over 8 malware families. NeurIPS 2024 Datasets and Benchmarks track.
- Made by
- Guo et al. (Bo Li lab)
- Released
- November 2024
- Kind
- Secure code and review
- Level
- Expert
- Scored
- Graded by a model
- Answers
- Agent task
- Tasks
- All public
- Strongest model tested
-
Muse Spark 1.3 #26 on the capability index
- Last in a system card
- October 2026
- Last model added
- October 2026
In the authors’ words
With the rapidly increasing capabilities and adoption of code agents for AI-assisted coding, safety concerns, such as generating or executing risky code, have become significant barriers to the real-world deployment of these agents. To provide comprehensive and practical evaluations on the safety of code agents, we propose RedCode, a benchmark for risky code execution and generation: (1) RedCode-Exec provides challenging prompts that could lead to risky code execution, aiming to evaluate code agents' ability to recognize and handle unsafe code. We provide a total of 4,050 risky test cases in Python and Bash tasks with diverse input formats including code snippets and natural text. They covers 25 types of critical vulnerabilities spanning 8 domains (e.g., websites, file systems). We provide Docker environments and design corresponding evaluation metrics to assess their execution results. (2) RedCode-Gen provides 160 prompts with function signatures and docstrings as input to assess whether code agents will follow instructions to generate harmful code or software. Our empirical findings, derived from evaluating three agent frameworks based on 19 LLMs, provide insights into code agents' vulnerabilities. For instance, evaluations on RedCode-Exec show that agents are more likely to reject executing risky operations on the operating system, but are less likely to reject executing technically buggy code, indicating high risks. Risky operations described in natural text lead to a lower rejection rate than those in code format. Additionally, evaluations on RedCode-Gen show that more capable base models and agents with stronger overall coding abilities, such as GPT4, tend to produce more sophisticated and effective harmful software. Our findings highlight the need for stringent safety evaluations for diverse code agents. Our dataset and code are available at https://github.com/AI-secure/RedCode.
Muse Spark 1.3 leads with 6.00%
Best score per model as labs report them in their own cards. Labs pick their own settings, so these compare less cleanly than independent runs.
- 1
Muse Spark 1.3 6.00%
- 2
Muse Wonder Full 8.00%
- 3
Muse Spark 1.1 12%
Source: Labs’ model cards
| # | Model | Score | Setting | Date | Source |
|---|---|---|---|---|---|
| 1 | | 6.00% | Oct 2026 | Lab model card | |
| 2 | | 8.00% | Oct 2026 | Lab model card | |
| 3 | | 12% | Jul 2026 | Lab model card |
3 models have held number one in labs’ own numbers since its release in November 2024
Lab claims count from the day the card came out, independent runs from the model’s release.
Source: Labs’ model cards
Scores over time
All the scores we have, one dot each, so a model tested at several settings appears more than once.
Source: Labs’ model cards
Labs report it only in system cards
We read the headline results of 522 launch posts from 52 labs, and none of them list this benchmark. Some system cards do, below.
3 system cards report it, from 1 lab
Besides launch posts, we read the system cards, model cards and technical reports labs publish with a release. They report far more, including safety and frontier-risk tests.
| Date | Document | Score | As the document writes it | Section |
|---|---|---|---|---|
| Oct 23, 2026 | | 6 | RedCode ASR averaged over single-turn and multi-turn, Muse Spark 1.3 (API) (Figure 15) | Cyber risk |
| Oct 12, 2026 | | 8 | RedCode multi-turn ASR, lower is better (Cyber Robustness Evaluations table, section 4). Single turn 9.0 | Cyber risk |
| Jul 9, 2026 | | 12 | RedCode multi-turn ASR, Muse Spark 1.1 model-only (Figure 20 text). Single-turn 8.0. System 7.0 and 12.0 | Cyber risk |
More in Cybersecurity
- ExploitGym In use 869 real-vulnerability exploit-development tasks (userspace, V8, Linux kernel). Success means capturing a flag through the intended vulnerability. GPT-6 Astra 42.4%
- ExploitBench In use 41 recent V8 JavaScript-engine N-day vulnerabilities. Progress measured by 16 grader-verified capability flags across five tiers. GPT-6 Astra 100%
- CyberBench v1.1 (Vals) In use Agents work on OSS-Fuzz memory-safety bugs from ARVO images in two tracks. They write a proof-of-concept input that crashes the target, or patch the source so the crash stops and tests still pass.
Muse Wonder 80.4%
- SRE-Bench In use Software reverse engineering without source: 262 binary instances from 19 private programs, each with six graded objectives. GPT-6 Astra 56.9%
- CyScenarioBench In use Scenario-based long-horizon security challenges in sandboxes, organized in task, scenario and campaign tiers. Evaluation set kept private.
Gemini 4 Argon 100%
- ExploitBench - Internal Port In use Agents develop working exploits for recently disclosed vulnerabilities to limit contamination. Scored as arbitrary code execution success rate. GPT-6 Cyber 42%