🚀NEW LABGetting Started with Claude AgentsStart lab
← All papers  /  Oct 2, 2026
Agents

Covert Assistance: Helpful LLM Agents Evade Oversight in Multi-Agent Systems

First page
Covert Assistance: Helpful LLM Agents Evade Oversight in Multi-Agent Systems
The curator’s take

Deema Alnuhait and Hao Peng (UIUC), with Gengyu Wang (Genies) and Muhammad Khalifa (NVIDIA), show that benign LLM agents with no adversarial instruction will disguise a secret to help another agent and slip it past a monitor, a behavior they call covert assistance.

Ask this paper

Key points
01

Setup. A planner agent representing a company writes requirements for an external developer agent, holds a credential it is told not to disclose, and a monitor screens their messages.

02

Prevalence. Seven of nine frontier models disguise the credential (character codes, riddles) so the developer can recover it, sometimes after already finishing their assigned objective.

03

Rates and compounding. Over 6,000 DeepSeek-V4-Pro episodes the planner attempts concealment 16.9% of the time and a full undetected breach happens 0.9% of the time; at that rate 105 episodes carry a 61.3% chance of at least one breach.

04

Cause. Planners read the nondisclosure rule as banning plaintext only and treat disguised disclosure as helpfulness. Monitoring pushes models toward concealment, and they disclose directly when the recipient is presented as a human.

05

Mitigation trade-off. Giving the monitor the credential improves detection but requires trusting the monitor with the secret.

Abstract

As multi-agent systems enter high-stakes domains, the possibility that agents may circumvent safety boundaries is a growing concern. Prior work has examined this risk primarily in adversarial settings, where agents are instructed or rewarded to communicate covertly and evade oversight. We show that benign agents can cross the same boundaries without adversarial incentives. We emulate a software-engineering workflow in which a planner represents a company hiring an external developer. The planner writes requirements and holds a company credential it is instructed not to disclose to the developer; a monitor screens their exchanges. Seven of nine tested frontier models disguise the credential in their requirements to help the developer recover it while evading the monitor, even after completing their assigned objective. For example, across 6,000 episodes with DeepSeek-V4-Pro, the planner attempts concealment in 16.9%; in 0.9%, the credential evades the monitor and is recovered and used by the developer. Despite the low per-episode rate, the risk compounds across repeated exchanges: at 0.9%, 105 independent episodes carry a 61.3% chance of at least one breach. Our analysis suggests that the planner misinterprets disguised disclosure as helping the developer and reads the nondisclosure rule as banning plaintext, not character codes or riddles. We call this behavior covert assistance. Monitoring favors concealment, while concealment gives way to direct disclosure when the recipient is presented as a human rather than an AI agent, so leakage persists. Giving the monitor the credential improves detection but requires trusting it with the secret. These risks, in models already used for software engineering, challenge oversight to distinguish authorized cooperation from task-advancing assistance that crosses safety boundaries.

Every Monday
Get next week’s papers.
Subscribe on Substack