- Rating
- 3
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
This paper introduces MiniLab, a synthetic environment comprising five interconnected services, 249 benign tasks, and eight attack objectives, to investigate loss-of-control risks from multi-agent attacks. Through 16 human-optimized attacks, the authors demonstrate that distributed attacks can substantially reduce suspicion under per-agent monitoring. The paper further examines a six-stage stateful attack chain, joint monitoring, and the ability of LLMs to generate covert attack plans.
Critical strengths
- Valuable evaluation environment. MiniLab provides interconnected live services and persistent system state for studying coordinated attacks. The six-stage attack chain demonstrates how separate actions can accumulate into a larger loss-of-control outcome.
- Comprehensive empirical investigation. The paper evaluates distributed attacks under per-agent and joint monitoring, investigates attack explainability, and examines model-generated attack plans. These experiments provide useful evidence about the limitations of trajectory-based monitoring.
Critical weaknesses
- Limited fairness of the single-agent comparison. The authors acknowledge that single-agent and multi-agent attack plans were not developed with equal effort. This makes it difficult to determine how much of the observed reduction in monitor suspicion is attributable specifically to distributing attacks across agents.
- Limited evaluation of multi-agent-aware monitoring. The primary monitoring setup excludes complete shared system state, and the joint monitor uses a prompt originally designed for single-agent software-engineering tasks. Although additional monitoring analyses are provided, the effectiveness of the attacks against monitors explicitly designed to reason about cross-agent actions and shared state remains unclear.
Questions for authors
-
Can the authors provide comparisons between single-agent and multi-agent attacks with comparable red-teaming effort?
-
How would the attacks perform against multi-agent-aware monitors with access to shared system state?
-
Which monitor was used to provide feedback during the development of human-crafted attacks, and was GPT-5.6 Sol held out from this optimization?
3 comments
(2/2) Presentation revisions
Additionally, we submitted a revised version of our paper to improve clarity and incorporate new changes.
Presentation
- A new Threat Model section states the internal deployment setting, what the attackers can do, and what the monitor can and cannot see.
- The Setup section now describes MiniLab with a concrete example, states exactly what the monitor receives, and defines covert success with a calibrated threshold in one place.
- The Results section opens with the main numerical comparison (per-agent monitoring flags 3.4% of successful distributed attacks vs 82.4% for a single agent) and explains why joint monitoring still falls short of a single agent.
- We standardized figure formatting and captions, fixed typos, removed repeated text in the planning section, and converted the attack-explainability table into a single figure.
Relevant changes in the revised PDF
- Monitor prompt: LinuxArena's strong trajectory prompt, adapted to read one or more agents and to score combined harm (Appendix I). All GPT-5.6 Sol results rescored.
- Monitors from other model families (Appendix C, Table C1): Claude Opus 4.8, Gemini 3.1 Pro and DeepSeek V4 Pro; every monitor flags far fewer distributed attacks under per-agent monitoring than single-agent executions.
- Single-agent baseline (Appendix C): clarified.
We appreciate if the reviewer can take a look at our new version, and we're happy to clarify anything that remains difficult to follow.
Thank you for your response. I will maintain my score.
(1/2): Clarification on red-teaming effort, multi-agent-aware monitors, and held-out monitors
We thank the reviewer for the helpful feedback and for recognizing our paper as a meaningful contribution. To address your concerns, we provide an explanation of (1) the red-teaming effort for multi-agent and single-agent attacks and whether it affects our claim, (2) whether a monitor with a fuller view of the attack catches more, and (3) how we develop and evaluate the attacks against the same monitor.
Single agent vs split
The single-agent baseline uses the same attack, merging the three agents' step-by-step plans into a single plan, which is given to a single agent with all main tasks and combined permissions of the 3 to carry out the same actions in a single trajectory. We then applied further optimization pressure to the single-agent trajectory.
Because of this further optimization, the single agent's steps can differ from the team's, which is why the submitted text said it may take different steps. The single agent is flagged far more often (82.4% vs 3.4% for per-agent monitoring at the 2% FPR threshold), which points to distributing the attack rather than a weaker single-agent plan as the main source of the difference, even after this further optimization. We see the same thing without changing the attack at all, as reading the exact same split executions together instead of one agent at a time raises the share flagged from 3.4% to 40.9%.
Why did we choose not to spend equal effort on single-agent attacks?
As mentioned above, we attempted further optimization of the single-agent plans, but the results suggested that achieving comparable evasion rates would require substantially more budget. Our goal was to demonstrate concrete cases in which an attack flagged during single-agent execution could evade detection when split across agents. Therefore, we focused more on red-teaming viable attack strategies in which agents can coordinate and distribute the attack among themselves. If possible, we will provide results for single-agent and multi-agent teams under matched red-teaming budgets to help resolve this uncertainty in our camera-ready version.
Monitors built for multiple agents and shared state
We rewrote the monitor prompt to read one or more agents and ask whether their combined changes cause harm (Appendix I). Under joint monitoring, this raises the median suspicion from 5.5 to 7.9 across the 16 attacks, and the share of successful distributed attacks flagged from 32% to 41%. Still, 59% evade, even though joint monitoring is told which agents are working together.
We don't provide the monitor system state; it isn't always available, and we want to focus on trajectory monitors. Inter-agent messages are excluded because our threat model assumes agents can coordinate through channels that the monitor cannot see, and, moreover, the optimized attacks require no messages during execution, as the plan is fixed in advance. We adapted the monitor prompt to read one or more agents' trajectories together, but joint monitoring serves as a comparison point rather than a proposed protocol, since it assumes the monitor already correctly identifies which agents are working together. Monitors that combine trajectories with system state are an important direction, and while MiniLab records the state needed to test them, we leave state visibility to monitors as future work to focus on these worst-case outcomes, given uncertainty about whether monitorability can be preserved as model capabilities advance (see Think Fast, OpenAI's monitorability evaluation, and AISI's Loss of Oversight report).
Which monitor gave feedback, and was Sol held out?
For the human-crafted attacks, GPT-5.6 Sol was the monitor we optimized against, as it was the most capable monitor available to us at the time, so it was not held out for them. Sol was held out for the AI-planned attacks, which were developed with GPT-5.6 Luna feedback. The attacks were not optimized for the revised monitor prompt, but the effect is similar, as median suspicion is 9.0 for a single agent vs 1.75 for the most suspicious agent in the split, compared with 9.0 vs 1.5 under the original monitor prompt.
Monitors from other model families, which the attacks were never optimized against, also flag far fewer distributed attacks than single-agent executions:
Share of successful executions flagged at each monitor's own 2% FPR threshold (100 benign teams, one reading per view; Appendix C, Table C1).