Skip to content
Sprint projectMar 23, 2026Cambridge, UK

LidaRed: ControlArena Red-Team Dataset Generator

Linh Le, David Williams-King · Team Lida Safety

Submitted to AI Control Hackathon 2026. Sprint projects are early-stage work by participants, not Apart Research publications.

Read the report

Report: LidaRed: ControlArena Red-Team Dataset Generator

Code (opens in new tab)
Share

We present LidaRed, an automated pipeline for generating adversarial red-team datasets for AI control. Built on the ControlArena benchmark, our pipeline iteratively refines attacks using monitor feedback, with a focus on omission-based attacks. We achieve attack success rates of up to 60% against Claude Opus 4.6 as a safety monitor, demonstrating that current frontier models still cannot catch subtle side task execution.

Reviews

Judging this Sprint?

Review this project

Your public critique appears on this page without your name. Your private critique is not published; only the Apart team reads it. If you agree below, we share your review with grantmaking.ai (opens in new tab) and the Transformative AI Fund so strong projects can be funded.

Not shown on this page.

Shown on this page, without your name.

Only the Apart team reads this, and funders if you agree below.

Share my name publicly on grantmaking.ai *
Share my private critique with funders *

How much would this matter for AI safety if it worked? How innovative is it? For scores of 4-5: is this actually new to the field, or replicating recent work?

Scoring guide
  1. 1Negligible. No clear problem addressed, or no meaningful novelty.
  2. 2Limited. Addresses a real problem but with a generic or well-trodden approach. Incremental at best.
  3. 3Moderate. Clear problem with a reasonable approach; some novelty in framing or method beyond routine application of existing tools.
  4. 4Significant. Important problem with an original approach, or identifies a neglected problem area. A valuable contribution others could build on.
  5. 5Exceptional. Tackles a critical AI safety problem with a genuinely novel approach, or opens a new research direction. Clear theory of change. You'd be excited to share this with researchers in the area.

How sound are methodology, implementation, and findings?

Scoring guide
  1. 1Seriously flawed. Methodology broken, results uninterpretable, or implementation doesn't work.
  2. 2Weak. Approach has significant gaps: missing validation, flawed experimental design, or incomplete implementation.
  3. 3Competent. Technically solid given the short duration. Methodology makes sense, results are interpretable, limitations acknowledged, work builds toward clear conclusions.
  4. 4Strong. Thorough methodology with convincing validation. Results clearly support conclusions. Immediately useful for future work.
  5. 5Exceptional. Ambitious scope executed rigorously. Surprising findings, novel methods, or unusually robust validation.

How clearly are work, findings, and impact potential communicated?

Scoring guide
  1. 1Incomprehensible. Cannot determine what the project is actually claiming or doing.
  2. 2Hard to follow. Key information buried, missing, or diluted by excessive length. Significant effort to extract main points.
  3. 3Clear enough. Can understand the problem, approach, and results without undue effort. Core content clearly present: problem, method, findings, limitations.
  4. 4Well presented. Easy to follow, well-structured, appropriate level of detail. Target audience would get it quickly.
  5. 5Exceptionally clear. A pleasure to read. Complex ideas made accessible. Could serve as a model for how to present this type of work.

  1. Here is a list of my thoughts:

    1. I'm unsure of the problem you are trying to solve with this project. You have generated some trajs from the Control Arena benchmark. I'm unsure what value that provides.

    2. Given that the value is a dataset, the dataset itself seems very limited.

    3. I really like that the write-up is clean and well presented.

    4. In the abstract, you state you "iteratively refined attacks using monitor feedback, with a focus on omission-based attacks", However, this is not talked about in your methods. This suggests to me that the method lacks the detail needed if someone was to replicate your work.

    5. You state a key finding about omission-based attacks being hard to detect; however, I'm unsure how you proved this from your results. This could just be because of the data set you used, or randomness instead. If you don't have hard evidence (as that's hard to get in a hackathon), then maybe saying these findings in a discussion may be more appropriate.

    Given that, good work on making a paper in 3 days! It's no easy task.

    Read full reviewShow less
  2. - clear code and clearly written, interesting idea simply and effectively presented, enjoying reading it ;)

    - further comments intended to think of what this would look like as a full paper, and where the research direction seems to point to.

    - iterative improvements are great, but there’s no discussion of the actual rewrites that are made to the prompts in order to bypass the monitor - this would be very interesting to look at. a simple case study of a couple prompts would be great. the framework itself seems novel well suited to current trends / agentic use of LMs

    - makes sense that omission in the networking example is harder to detect - you're testing the model's conception of an "ideal configuration" here, or the ability to construct a configuration - so you should first establish if this is something that the model knows at all, or some baseline for what safety looks like in your network scenario. for Claude Opus I imagine that this is reasonable to assume that this is known, but it should still be tested

    - what’s the so what? this reads like a SWE scaffold to more effectively bypass safety screens. Iterating from feedback is not novel, though finding specific techniques that work is. How could this be meaningfully used to improve existing safety regimes - is this for refining evals?

    Read full reviewShow less

Cite this project

@misc{le2026lidared,
  title = {{LidaRed: ControlArena Red-Team Dataset Generator}},
  author = {Linh Le and David Williams-King},
  year = {2026},
  month = mar,
  note = {Submitted to AI Control Hackathon 2026, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/lidared-controlarena-redteam-dataset-generator-uirn}},
  url = {https://apartresearch.com/sprints/projects/lidared-controlarena-redteam-dataset-generator-uirn}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026