Skip to main content

Impact & Exfiltration

Sep 2026

BlueBench-Simulation-003: Three simulated end-of-intrusion investigations (ransomware impact, backup sabotage, and data exfiltration) scored against complete hidden ground truth

Metric
Track
View
Provider
3 tasks · 24 models · Sep 2026
RankModels (24)ScoreSpread?Highest minus lowest score across recorded tasks and trials (percentage points). Lower is less variable.$/taskLat
1
Claude Opus 5.5
89.8%25.7pp$5.1716m 53s
2
GPT-6 Astra
88.0%31.7pp$12.108m 57s
3
Claude Sonnet 5.5
83.4%42.7pp$1.297m 5s
4
GPT-5.6 Sol
81.2%76.0pp$5.7013m 15s
5
GPT-6.1 Sol
81.2%26.2pp$1.9011m 17s
6
Grok 4.6
80.6%52.4pp$8.6326m 42s
7
Gemini 4 Argon
79.3%36.6pp$19.2225m 22s
8
Claude Opus 4.8
70.5%76.4pp$3.5613m 45s
9
GPT-6 Sol
70.0%49.0pp$3.0414m 51s
10
GLM-5.3 Flash
69.6%62.7pp$0.168m 28s
Best ScoreBest Open Weight
Dataset
BlueBench-Simulation-003
3 tasks
Task Types
Incident Response·2 tasks(67%)
Detection Engineering·1 task(33%)
Incident Response
Detection Engineering
Simulation
Ransomware
Backup Sabotage
Data Exfiltration
Windows
Linux

About BlueBench-Simulation

BlueBench-Simulation takes a different approach from our intrusion benchmarks. Instead of replaying one real compromise, every environment is a fully generated enterprise environment: routine baseline activity, a simulated intrusion, and matched benign lookalikes designed to punish pattern-matching without verification. Because we author the environment, the ground truth is complete and none of the data can have leaked into training sets. Every case starts from a single weak alert; detection queries are scored deterministically and free-form reports are graded against the hidden rubric by a single fixed LLM judge.

The series splits twelve authored investigations along the attack lifecycle across three benchmarks: 001 Initial Access & Command-and-Control, 002 Identity & Active Directory Attacks, and 003 Impact & Exfiltration.

About This Benchmark

This benchmark covers the end of the kill chain. The three tasks are about what attackers do at the end of an intrusion: an incident response investigation of ransomware impact across a Windows estate, buried under more benign lookalikes than any other case in the series plus a deliberately separable decoy data-export thread; an incident response investigation of backup-fleet sabotage on a Linux estate with messy, administrative-heavy telemetry; and a detection engineering assignment isolating unauthorized data exfiltration from an environment full of legitimate large outbound transfers.

Each case starts from a single weak alert, with several thousand raw events drawn from endpoint, network, and system telemetry. The two incident response reports are graded by the LLM judge; the detection query is scored deterministically. There are no open-ended threat hunts in this benchmark. The current export contains 24 models with three trials per task: 216 runs. Costs and latency are reported per evaluated task attempt.

Sample Questions

Incident Response

Q: Behavioral analytics flag elevated anomalous activity across multiple systems in a Windows estate. Investigate end to end and write a self-contained incident report: scope, affected hosts and accounts, attacker tradecraft, impact, and the response actions the situation warrants.

A: [Free-form report plus response-action choices scored against hidden rubrics]

Incident Response

Q: A backup-continuity alert fires on a Linux estate. Determine whether backup integrity has been compromised, reconstruct how, and write a self-contained incident report with the response actions the situation warrants.

A: [Free-form report plus response-action choices scored against hidden rubrics]

Detection Engineering

Q: Write a detection that returns the records constituting unauthorized data exfiltration in this environment, scoped to network connection telemetry. The environment carries many legitimate large outbound transfers; the detection must return only the malicious exfiltration.

A: [Read-only detection query re-executed against the case evidence and scored by exact-record F1]

Key Findings

Results

Claude Opus 5.5 had the highest benchmark score at 89.8%. The top results among 24 evaluated models were Claude Opus 5.5 (89.8%), GPT-6 Astra (88.0%), Claude Sonnet 5.5 (83.4%). These are observed scores on this benchmark.

Score by ModelTop 10 of 24
  1. 1Claude Opus 5.589.8%
  2. 2GPT-6 Astra88.0%
  3. 3Claude Sonnet 5.583.4%
  4. 4GPT-5.6 Sol81.2%
  5. 5GPT-6.1 Sol81.2%
  6. 6Grok 4.680.6%
  7. 7Gemini 4 Argon79.3%
  8. 8Claude Opus 4.870.5%
  9. 9GPT-6 Sol70.0%
  10. 10GLM-5.3 Flash69.6%

Track results

Incident Response: Claude Opus 5.5 led at 95.1%. Detection Engineering: GPT-6 Astra and GPT-5.6 Sol tied at 97.1%.

Open-weight results

GLM-5.3 Flash (69.6%) had the highest score among the 7 open-weight models evaluated. GLM-5.3 Flash cost $0.16/task.

Cost per task

GLM-5.3 Flash had the lowest measured cost at $0.16/task, with 69.6% benchmark score. Claude Opus 5.5 scored 89.8% at $5.17/task. Costs reflect the evaluated task mix and the stated pricing assumptions.

Cost per TaskTop 10 of 24
  1. 1GLM-5.3 Flash$0.16
  2. 2DeepSeek V4 Flash$0.31
  3. 3GPT-6 Luna$0.51
  4. 4Claude Haiku 5.5$1.07
  5. 5GPT-5.6 Luna$1.09
  6. 6DeepSeek V4 Pro$1.19
  7. 7Claude Sonnet 5.5$1.29
  8. 8MiniMax M3$1.59
  9. 9GLM-5.2$1.59
  10. 10GPT-5.6 Terra$1.79

Time per task

GPT-5.6 Terra had the lowest reported average latency at 4m 58s/task, with 66.3% benchmark score. Latency includes the work performed by the agent during evaluation.

Task Duration (avg)Top 10 of 24
  1. 1GPT-5.6 Terra4m 58s
  2. 2Claude Sonnet 5.57m 5s
  3. 3GPT-5.6 Luna8m 18s
  4. 4GLM-5.3 Flash8m 28s
  5. 5GPT-6 Astra8m 57s
  6. 6Claude Sonnet 510m 9s
  7. 7GPT-6.1 Sol11m 17s
  8. 8Gemini 3.6 Flash12m 39s
  9. 9GPT-5.6 Sol13m 15s
  10. 10Claude Opus 4.813m 45s

Reliability: score spread

Claude Opus 5.5 had the smallest observed score spread at 25.7 percentage points; its overall score was 89.8%. Spread is the highest minus lowest score across recorded tasks and trials. It includes differences in task difficulty and is not a measure of repeatability on one fixed task.

Score spread (percentage points)Top 10 of 24
  1. 1Claude Opus 5.525.7pp
  2. 2GPT-6.1 Sol26.2pp
  3. 3GPT-6 Astra31.7pp
  4. 4Gemini 4 Argon36.6pp
  5. 5Claude Sonnet 5.542.7pp
  6. 6GPT-6 Luna47.2pp
  7. 7GPT-6 Sol49.0pp
  8. 8Claude Opus 550.0pp
  9. 9Grok 4.652.4pp
  10. 10GLM-5.255.4pp

Run completion

23 of 24 models completed all recorded runs without an unrecoverable error. Completion does not imply a correct answer or rule out a refusal. Recorded refusals: GLM-5.3 (1), Claude Opus 5 (1). These attempts remain in the reported scores.

Task Completion RateTop 10 of 24
  1. 1Claude Opus 5.5100.0%
  2. 2GPT-6 Astra100.0%
  3. 3Claude Sonnet 5.5100.0%
  4. 4GPT-5.6 Sol100.0%
  5. 5GPT-6.1 Sol100.0%
  6. 6Grok 4.6100.0%
  7. 7Gemini 4 Argon100.0%
  8. 8Claude Opus 4.8100.0%
  9. 9GPT-6 Sol100.0%
  10. 10GLM-5.3 Flash100.0%

Measured Trade-offs

  • Claude Opus 5.5 — Highest observed benchmark score: 89.8% at $5.17/task.
  • GLM-5.3 Flash — Lowest measured cost: $0.16/task, with 69.6% benchmark score.

Methodology

Scoring

  • Score: Mean over three trials per task, scored against hidden rubrics authored with each environment. Detection engineering tasks are scored deterministically; free-form threat hunting and incident response reports are graded against the rubric by a single fixed LLM judge
  • Facts: Each rubric fact is a specific finding (a host, account, address, filename, or hash) the report must commit to. For report tasks the judge checks that the finding is actually asserted, not merely mentioned, and that it is tied to the evidence behind it; partial credit is per-fact, not per-report
  • Citations: Material claims must point at the evidence records they rest on; a correct finding without its supporting evidence earns reduced credit
  • Red herrings: Asserting a known benign lookalike as malicious applies a multiplicative penalty to the report; a violation is counted only when repeated independent judge passes agree
  • Detections: Submitted detection queries are re-executed against the case evidence and scored by exact-record F1 with no judge involved; rules that over-fire on the benign lookalikes lose precision
  • Cost / task: USD per logical evaluated task, including repeated attempts. A bundled question set counts its individual questions; a report counts once. Prompt caching is included; judge costs are excluded
  • Latency: Average elapsed time per logical evaluated task, using the export normalization for bundled question sets
  • Reliability / spread: On this page, highest minus lowest score across recorded tasks and trials, in percentage points (lower is tighter). The BlueBench reliability score is 100 minus the mean of these six spreads: inverted spread, not same-task repeatability

Environment Generation

  • Three fully generated enterprise environments: a Windows estate hit by ransomware, a Linux estate with a sabotaged backup fleet, and a Windows environment leaking data
  • Each environment is a small segmented enterprise with sustained baseline administration, deployment, backup, and monitoring activity
  • Simulated intrusions: staged ransomware impact with a decoy data-export thread, backup-integrity sabotage inside routine replication activity, and data exfiltration hidden among authorized bulk transfers
  • Matched benign red herrings in every case: authorized activity deliberately shaped to resemble the intrusion
  • Several thousand raw events per case across endpoint, network, and system log sources, exposed to the agent as raw files plus a queryable index

Task Design

  • Three tasks: two incident response investigations, one detection engineering assignment
  • Every task starts from a single alert framed as a lead, not a conclusion
  • Incident response produces free-form reports with response-action choices, graded against the hidden rubric by a single fixed LLM judge; detection engineering returns structured answers plus a detection query, scored deterministically
  • Agents are told to execute their detection query and inspect the results before submitting

Controls

  • Same system prompt for all models, no per-model tuning
  • "Thinking" mode enabled where available
  • Three trials per task (k=3); reported scores are means over all 9 runs per model
  • Refused or failed runs score whatever they earn; nothing is excluded from the averages

System Prompt

System
You are a security analyst working an active case in Cotool. Available tools: - Execute commands in an isolated sandbox. - Write analysis scripts to a working directory. Case evidence: - Raw, heterogeneous telemetry for the case, plus a read-only queryable index over every record. - A manifest listing the source formats and record counts. Working requirements: - Treat the incoming alert as a lead, not a conclusion. - Work from raw evidence, correlate across source families, and preserve uncertainty. - Citations must reference the exact records returned by the evidence index. - Detection queries must be read-only and return the matching record identifiers. - Before submitting a detection query, execute it and inspect its result count and representative rows.
User
[Raw alert JSON] + Investigate this case end to end and write a single comprehensive report as your final response. The alert is a weak lead, not a conclusion. Proactively hunt across all of the available telemetry to determine what is actually happening. Correlate across source families and cite the specific evidence behind each material claim. Be rigorous about the limits of the evidence: clearly separate what the telemetry establishes from what it does not.
[Alert + task instructions]

Paraphrased. Tool names, file paths, and the evidence schema given to the agent are omitted.

Caveats

  • Results describe the current export and its recorded task mix; counts of repeated attempts can differ across models.
  • Spread is the highest minus lowest score across recorded tasks and trials. Different task difficulty and question bundling affect it; it does not isolate same-task repeatability.
  • Costs are USD per evaluated task, including repeated attempts. Bundled question sets use logical question counts; each report attempt is counted once. Provider prompt caching is included and judge costs are excluded.
  • In a track-filtered view, the score changes but cost and latency remain the benchmark-wide averages; spread is shown only in the all-tracks view.
  • Report scores depend on LLM judging. Detection queries are executed against the evidence. Close scores do not establish a statistically significant ordering.

Other Benchmarks

Identity & Active Directory Attacks
Identity & Active Directory Attacks

BlueBench-Simulation-002: Four simulated Windows identity-tier attacks (password spray, domain persistence, credential-attack detection, and a hands-on-keyboard operator) scored against complete hidden ground truth

Simulation
Active Directory
Password Spray
Domain Persistence
Credential Access
Hands-on-Keyboard
Windows
4 samples · 24 models · Sep 2026
Initial Access & Command-and-Control
Initial Access & Command-and-Control

BlueBench-Simulation-001: Five simulated investigations covering a mail-borne endpoint compromise, a DMZ webshell, and DGA botnet beaconing, scored against complete hidden ground truth

Simulation
Initial Access
Command & Control
Mail Compromise
Webshell
DGA Botnet
Windows
Linux
5 samples · 24 models · Sep 2026
AWS Cloud Intrusion
AWS Cloud Intrusion

BlueBench-Intrusion-003: Real AWS intrusion through leaked CI credentials, testing detection engineering and evidence-backed investigation reports

AWS
Incident Response
CloudTrail
Identity
Persistence
Exfiltration
8 samples · 24 models · Sep 2026
Windows Enterprise Intrusion
Windows Enterprise Intrusion

BlueBench-Intrusion-002: Real multi-host Windows Active Directory intrusion spanning detection engineering, malware analysis, and open-ended incident reporting

Detection Engineering
Malware Analysis
Incident Response
Threat Hunting
Lateral Movement
Credential Access
Memory Forensics
40 samples · 24 models · Sep 2026
macOS Threat Investigation
macOS Threat Investigation

BlueBench-Intrusion-001: Real macOS infostealer intrusion spanning incident response, threat hunting, and detection engineering

Incident Response
Threat Hunting
Detection Engineering
macOS Forensics
Credential Access
Data Exfiltration
14 samples · 24 models · Sep 2026
NYU CTF Bench
NYU CTF Bench

Real CTF challenges from CSAW competitions covering reverse engineering, forensics, and miscellaneous problem-solving

Reverse Engineering
Forensics
Miscellaneous
81 samples · 11 models · Feb 2026
CyberMetric
CyberMetric

Multiple-choice cybersecurity knowledge evaluation across 10,000 questions

Standards & Certifications
Network Security
Cryptography
Risk Management
Access Control
Incident Response
Application Security
Cloud Security
10180 samples · 13 models · Feb 2026
Cybench (Defensive Subset)
Cybench (Defensive Subset)

Defensive security CTF challenges testing forensics, reverse engineering, and miscellaneous security skills

Forensics
Reverse Engineering
Miscellaneous
Hardware
18 samples · 10 models · Jan 2026
Sigma Detection Classification
Sigma Detection Classification

Multi-label classification of MITRE ATT&CK techniques from Sigma rules

Detection Engineering
MITRE ATT&CK
SIEM
Windows
Linux
Cloud
Network
Application
2733 samples · 12 models · Jan 2026
BOTSv3 Blue Team CTF
BOTSv3 Blue Team CTF

Blue team CTF scenarios testing incident response and threat hunting

Incident Response
Threat Hunting
Alert Triage
Log Analysis
Advanced Persistent Threat (APT)
Cloud Security (AWS/Azure)
51 samples · 15 models · Dec 2025

AI for the blue team.

Run Cotool's harness in your environment to get real security work done

Book a demo