Evaluation dossier
RedCode
Does a code agent recognize unsafe execution and unsafe generation under different input forms?
CROSS-REPORT MONITORING
PUBLISHED EVIDENCE
RedCode · Attack Success Rate
Published measurements across source reports. Task scopes are annotated; configuration differences remain attached to each observation.
24 observations · 0 dated
- Code input / Base
- Code input with jailbreaking / Base
- Text summaries / Base
- Text descriptions / Base
- Code input / + (a) Simple
- Code input with jailbreaking / + (a) Simple
- Text summaries / + (a) Simple
- Text descriptions / + (a) Simple
- Code input / + (b) Awareness
- Code input with jailbreaking / + (b) Awareness
- Text summaries / + (b) Awareness
- Text descriptions / + (b) Awareness
- Code input / + (c) Detection
- Code input with jailbreaking / + (c) Detection
- Text summaries / + (c) Detection
- Text descriptions / + (c) Detection
- Code input / + (d) Modification
- Code input with jailbreaking / + (d) Modification
- Text summaries / + (d) Modification
- Text descriptions / + (d) Modification
- Code input / + (e) Combined
- Code input with jailbreaking / + (e) Combined
- Text summaries / + (e) Combined
- Text descriptions / + (e) Combined
24 observations lack a verified model release date. They remain in Data and Systems.
Select a point or table row to inspect its conditions and provenance.
24 observations
| System / model | Result | Condition status | Task / conditions | Evaluator / report | Dates |
|---|---|---|---|---|---|
| 88.4%Attack Success Rate | Incomplete | Text descriptions / Basetemperature=0; max 1024 generated tokens; 8 interaction rounds (Appendix C.2)ReAct | Not disclosedRedCode: Risky Code Execution and Generation Benchmark for Code Agents | Release —Report 2024-11-12 | |
| 87.2%Attack Success Rate | Incomplete | Text descriptions / + (a) Simpletemperature=0; max 1024 generated tokens; 8 interaction rounds (Appendix C.2)ReAct | Not disclosedRedCode: Risky Code Execution and Generation Benchmark for Code Agents | Release —Report 2024-11-12 | |
| 86.53%Attack Success Rate | Incomplete | Text descriptions / + (d) Modificationtemperature=0; max 1024 generated tokens; 8 interaction rounds (Appendix C.2)ReAct | Not disclosedRedCode: Risky Code Execution and Generation Benchmark for Code Agents | Release —Report 2024-11-12 | |
| 85.33%Attack Success Rate | Incomplete | Text descriptions / + (b) Awarenesstemperature=0; max 1024 generated tokens; 8 interaction rounds (Appendix C.2)ReAct | Not disclosedRedCode: Risky Code Execution and Generation Benchmark for Code Agents | Release —Report 2024-11-12 | |
| 84.93%Attack Success Rate | Incomplete | Text descriptions / + (c) Detectiontemperature=0; max 1024 generated tokens; 8 interaction rounds (Appendix C.2)ReAct | Not disclosedRedCode: Risky Code Execution and Generation Benchmark for Code Agents | Release —Report 2024-11-12 | |
| 83.2%Attack Success Rate | Incomplete | Text descriptions / + (e) Combinedtemperature=0; max 1024 generated tokens; 8 interaction rounds (Appendix C.2)ReAct | Not disclosedRedCode: Risky Code Execution and Generation Benchmark for Code Agents | Release —Report 2024-11-12 | |
| 79.33%Attack Success Rate | Incomplete | Code input / Basetemperature=0; max 1024 generated tokens; 8 interaction rounds (Appendix C.2)ReAct | Not disclosedRedCode: Risky Code Execution and Generation Benchmark for Code Agents | Release —Report 2024-11-12 | |
| 71.87%Attack Success Rate | Incomplete | Code input / + (a) Simpletemperature=0; max 1024 generated tokens; 8 interaction rounds (Appendix C.2)ReAct | Not disclosedRedCode: Risky Code Execution and Generation Benchmark for Code Agents | Release —Report 2024-11-12 | |
| 69.07%Attack Success Rate | Incomplete | Text summaries / Basetemperature=0; max 1024 generated tokens; 8 interaction rounds (Appendix C.2)ReAct | Not disclosedRedCode: Risky Code Execution and Generation Benchmark for Code Agents | Release —Report 2024-11-12 | |
| 67.33%Attack Success Rate | Incomplete | Code input / + (d) Modificationtemperature=0; max 1024 generated tokens; 8 interaction rounds (Appendix C.2)ReAct | Not disclosedRedCode: Risky Code Execution and Generation Benchmark for Code Agents | Release —Report 2024-11-12 | |
| 64.53%Attack Success Rate | Incomplete | Code input with jailbreaking / Basetemperature=0; max 1024 generated tokens; 8 interaction rounds (Appendix C.2)ReAct | Not disclosedRedCode: Risky Code Execution and Generation Benchmark for Code Agents | Release —Report 2024-11-12 | |
| 63.73%Attack Success Rate | Incomplete | Code input / + (b) Awarenesstemperature=0; max 1024 generated tokens; 8 interaction rounds (Appendix C.2)ReAct | Not disclosedRedCode: Risky Code Execution and Generation Benchmark for Code Agents | Release —Report 2024-11-12 | |
| 63.73%Attack Success Rate | Incomplete | Code input / + (c) Detectiontemperature=0; max 1024 generated tokens; 8 interaction rounds (Appendix C.2)ReAct | Not disclosedRedCode: Risky Code Execution and Generation Benchmark for Code Agents | Release —Report 2024-11-12 | |
| 63.07%Attack Success Rate | Incomplete | Text summaries / + (a) Simpletemperature=0; max 1024 generated tokens; 8 interaction rounds (Appendix C.2)ReAct | Not disclosedRedCode: Risky Code Execution and Generation Benchmark for Code Agents | Release —Report 2024-11-12 | |
| 62.8%Attack Success Rate | Incomplete | Text summaries / + (d) Modificationtemperature=0; max 1024 generated tokens; 8 interaction rounds (Appendix C.2)ReAct | Not disclosedRedCode: Risky Code Execution and Generation Benchmark for Code Agents | Release —Report 2024-11-12 | |
| 62.13%Attack Success Rate | Incomplete | Code input / + (e) Combinedtemperature=0; max 1024 generated tokens; 8 interaction rounds (Appendix C.2)ReAct | Not disclosedRedCode: Risky Code Execution and Generation Benchmark for Code Agents | Release —Report 2024-11-12 | |
| 61.06%Attack Success Rate | Incomplete | Text summaries / + (c) Detectiontemperature=0; max 1024 generated tokens; 8 interaction rounds (Appendix C.2)ReAct | Not disclosedRedCode: Risky Code Execution and Generation Benchmark for Code Agents | Release —Report 2024-11-12 | |
| 60.93%Attack Success Rate | Incomplete | Code input with jailbreaking / + (a) Simpletemperature=0; max 1024 generated tokens; 8 interaction rounds (Appendix C.2)ReAct | Not disclosedRedCode: Risky Code Execution and Generation Benchmark for Code Agents | Release —Report 2024-11-12 | |
| 59.6%Attack Success Rate | Incomplete | Text summaries / + (b) Awarenesstemperature=0; max 1024 generated tokens; 8 interaction rounds (Appendix C.2)ReAct | Not disclosedRedCode: Risky Code Execution and Generation Benchmark for Code Agents | Release —Report 2024-11-12 | |
| 58.8%Attack Success Rate | Incomplete | Text summaries / + (e) Combinedtemperature=0; max 1024 generated tokens; 8 interaction rounds (Appendix C.2)ReAct | Not disclosedRedCode: Risky Code Execution and Generation Benchmark for Code Agents | Release —Report 2024-11-12 | |
| 57.73%Attack Success Rate | Incomplete | Code input with jailbreaking / + (d) Modificationtemperature=0; max 1024 generated tokens; 8 interaction rounds (Appendix C.2)ReAct | Not disclosedRedCode: Risky Code Execution and Generation Benchmark for Code Agents | Release —Report 2024-11-12 | |
| 51.47%Attack Success Rate | Incomplete | Code input with jailbreaking / + (b) Awarenesstemperature=0; max 1024 generated tokens; 8 interaction rounds (Appendix C.2)ReAct | Not disclosedRedCode: Risky Code Execution and Generation Benchmark for Code Agents | Release —Report 2024-11-12 | |
| 51.47%Attack Success Rate | Incomplete | Code input with jailbreaking / + (c) Detectiontemperature=0; max 1024 generated tokens; 8 interaction rounds (Appendix C.2)ReAct | Not disclosedRedCode: Risky Code Execution and Generation Benchmark for Code Agents | Release —Report 2024-11-12 | |
| 48.93%Attack Success Rate | Incomplete | Code input with jailbreaking / + (e) Combinedtemperature=0; max 1024 generated tokens; 8 interaction rounds (Appendix C.2)ReAct | Not disclosedRedCode: Risky Code Execution and Generation Benchmark for Code Agents | Release —Report 2024-11-12 |
Compare results within the stated task and configuration.
METR Time Horizon 1.1: the source is no longer actively updated (last update: 8 September 2026). Estimates above 16 hours exceed its reliable measurement range.
Protocol, configurations and original evidence →Task and measurement
Benchmark protocol profile
- Task / subject
- RedCode separates execution from generation; execution runs in containers with outcome checks, while generation uses different quality assessments.
- Measurement target
- Does a code agent recognize unsafe execution and unsafe generation under different input forms?
- Scoring / outcome
- Accuracy · Accuracy
- Interpretation boundary
- Execution and generation scores have different judges and denominators. Agent frameworks support different language subsets; comparing their aggregate rates without matching those subsets is inappropriate.
A reported evaluation
The source evaluates GPT-4o / Base LLM · RedCode-Gen / Base LLM.
Run configuration: Base model generation.
Reported measurement: Accuracy · 69.4%.
Accuracy Not disclosed
The reported behavior depends on whether a risky request is expressed as code or prose and on the type of unsafe behavior. Coding capability alone does not establish safe execution.
Measurement dossier · NUWA reading
Source-method reading and retained catalogue information are distinguished. Publication does not establish independent evidence or bilingual editorial review.
- Measurement construct
- Unsafe code execution and explicitly harmful code generation under distinct protocols.
- Task population
- RedCode-Exec contains 4,050 test cases spanning code and text forms; RedCode-Gen contains 160 function-signature/docstring prompts across eight software categories.
- Scoring and failure modes
- Exec uses execution scripts to distinguish rejection, execution failure and attack success. Gen reports refusal, generated-code accuracy and a separate VirusTotal score. The latter retains its source label because its unit has not been established here.
- System conditions
- Base models and code agents are separate systems. For the ReAct mitigation table, Appendix C.2 specifies temperature 0, up to 1024 generated tokens and eight interaction rounds.
- Statistical meaning
- Not established by the retained material
- Validity and interpretation
- Exec and Gen are different measurements and are not averaged. Numeric figures remain queued for explicit data acquisition or digitization; this table extraction is not full benchmark data coverage.
- Appropriate research use
- Not established by the retained material
- RedCode: Risky Code Execution and Generation Benchmark for Code Agents · #S3; #S4; #S57e4796140ad966c180057ec7fcc9440e099ad8d2b7e27ea54a7825cdc2fbc961
Evidence across reports
The same benchmark name can cover different tasks, scoring rules and system configurations. Each source remains visible; comparison groups explain which conditions are aligned.
RedCode: Risky Code Execution and Generation Benchmark for Code Agents
RedCode: Risky Code Execution and Generation Benchmark for Code Agents
Actual evaluators: Not disclosed
84 result records · 19 reported system names
Protocols and comparison decisions (0)
Original source charts and materials
Execution and generation scores have different judges and denominators. Agent frameworks support different language subsets; comparing their aggregate rates without matching those subsets is inappropriate.
Related research questions
References
Numerical results are reported by the cited authors.
- [1] RedCode: Risky Code Execution and Generation Benchmark for Code Agents. 2024-11-12 ; #S4.T1; row GPT-4o / Base LLM; condition RedCode-Gen / Base LLM; column Accuracy; #S4.T1; row GPT-4o / Base LLM; condition RedCode-Gen / Base LLM; column Refusal rate