A probe spotted agents about to leak a credential—but stopping them came at a cost
In a controlled preprint, an activation probe caught 31 of 38 Qwen3-32B disclosure calls. Yet a per-call alarm would have interrupted most otherwise refusing episodes, limiting the case for deployment.
The short version
- What happened
- Across six mocked workplace scenarios, two open-weight models faced up to 20 rounds of requests to reveal a fake protected value; no real credential, network or production system was involved.
- Who it affects
- For people responsible for production agents, an early-warning monitor could create a review point before a credential leaves the model. The same policy could also stop many agents that would ultimately refuse, creating workload and service disruption.
- What remains unproven
- Unreviewed preprint
Keep in mind
Unreviewed preprint
Two open-weight models
Six mocked workplace scenarios
Fake protected strings
No live credential or network
Warning strongest on the leaking call
Trained text baseline nearly matched the activation probe
Permitted disclosures could trigger alarms
Some operating points selected on test episodes
No independent replication
No separate funding or competing-interest statement located
Source analysis · 1 linked source. Primary analysed source date: 29 October 2026.
Keep following the evidence
Join The Impact Brief founding list for selected AI reports, their effect on people and the evidence limits. Read a sample first.
Read the full report · 4 min The evidence, methods, implications and limitations
The signal appeared just before disclosure
A new unreviewed study suggests an overseer can sometimes identify the exact model call that is about to reveal a protected value before the output is written. Researchers placed Qwen3-32B and gpt-oss-20b agents in six mocked workplace scenarios. A peer repeatedly asked for a fake deploy token, reserve price or other protected string, while the target's operator rule prohibited disclosure. Episodes ran for up to 20 rounds; control peers never asked for the value.
The researchers fitted linear probes to internal activations and kept test episodes separate from training. On Qwen3-32B test episodes, the last-prompt probe reached an AUROC of 0.98. At a threshold set to flag about 5% of benign control calls, it caught 31 of 38 leaking calls, compared with 10 of 38 for a zero-shot text monitor at a similar refusing-call rate. On gpt-oss-20b, a reasoning probe reached AUROC 0.91 and caught 14 of 26 leaking calls at its preset threshold.[1]
A useful warning is not yet a safe shutdown policy
The result weakens when the alarm has to govern a whole agent. Qwen episodes that never leaked contained a median 23 scored calls, so small per-call false-positive rates accumulated: 30 of 51 refusing episodes received at least one alarm. A stricter threshold limited alarms to two refusing episodes but caught only 10 of 38 leaking episodes. The warning also arrived mainly on the leaking call itself; prediction one call earlier was substantially weaker.
The probe largely detected an imminent disclosure rather than whether disclosure violated the rule. Permitted sharing could also trigger it, and a trained bag-of-words classifier came close to the activation probe, suggesting much of the advantage came from labelled training rather than privileged access to model internals. For security teams, the evidence supports further testing of pre-output review—not unattended deployment. Confidence would require independent replication, more models, realistic tools and credentials, adversarially reworded leaks, and alarm policies validated on previously unseen workplaces.[1]
The distinction that matters
What the same alarm threshold caught—and interrupted
The Qwen3-32B test set shows why a strong per-call score does not automatically make a practical stop rule.
Leaking calls
31 of 38 flagged
82% caught before output
Refusing calls
77 of 1,407 flagged
5.5% per-call alarm rate
Refusing episodes
30 of 51 saw an alarm
Most would be interrupted at least once
Watch the background, then check the evidence

Illustrative photo · not a video frame
The Royal Society · 2 min 31 sec · Background explainer
What is artificial intelligence? | The Royal Society
YouTube loads only when you choose; playback starts when you press play.
A short introduction to artificial intelligence from the Royal Society. Start here for basic concepts, then use current reporting to explore what has changed.
Evidence check: Published in 2018, before today’s generative AI tools. Useful for basic concepts, rather than an overview of current capabilities.
Published 2018-11-28. Source checked 14 October 2026. Check captions on the publisher’s video page.
Explore current AI technologyPhoto: ThisisEngineering / Unsplash · Licence
Continue the story
Read next
Continue exploring ai agents: compare the finding and its evidence limits.
What happens when a capable AI agent inherits a teammate’s bad work?
An unreviewed benchmark found that models which solved tasks alone often lost ground when a teammate pressured, misled or handed compromised work to them. Its 24,851 runs measure scripted scenarios—not human teamwork in live workplaces.
Read the next reportExplore the full source and evidence record
What this means for people
- For people responsible for production agents, an early-warning monitor could create a review point before a credential leaves the model. The same policy could also stop many agents that would ultimately refuse, creating workload and service disruption.
Global context
The experiment models a general multi-agent workplace conflict rather than one country or regulated sector. Real deployments differ in tools, access controls, languages, model providers and the consequences of both missed leaks and false stops.
What the evidence does not yet show
- Unreviewed preprint
- Two open-weight models
- Six mocked workplace scenarios
- Fake protected strings
- No live credential or network
- Warning strongest on the leaking call
- Trained text baseline nearly matched the activation probe
- Permitted disclosures could trigger alarms
- Some operating points selected on test episodes
- No independent replication
- No separate funding or competing-interest statement located
What to watch next
- Independent replication
- Tests on more model families
- Previously unseen tasks and organisations
- Encoded and reworded disclosures
- Alarm policies fixed before evaluation
- Human-review workload
- Comparisons with output filters and access controls
- Performance on real-but-safely-simulated tool use
Living evidence record
Impact record IAI-00O7RFI
Evidence stage
Studied
Confidence
Supported
Reporting basis
Source analysis
Independent or research support
Present
Record status
Monitoring
Last checked
31 October 2026
Source trail
1 direct source across 1 source type.
People impact
Documented in this record.
Uncertainty
Limits and next checks are explicit.
Stages describe the evidence available—not whether a technology is good or bad. See the public method.
Single-source reporting disclosure
This record analyses one direct source. It can establish what arXiv published or reported, but it is not independent corroboration of every performance claim or predicted outcome. The confidence label will change only when broader evidence is added.
Evidence trail
Sources used for this report
Links checked 31 October 2026
Research question, topics and regions
Predicting an AI agent's credential disclosure before its output is generated
Topics: AI agents · Credential security · Activation monitoring · Multi-agent systems · False alarms · AI oversight
Regions: Global
This report is labelled source analysis. We summarise and analyse source material in our own words; company statements remain attributed claims until independently supported. Translated summaries preserve the meaning of the original source and link back to it. Read our editorial standards.
Reader commentary
What does this mean where you are?
Tell us what you have seen at work, in your community or in everyday life. A question is welcome too. No account is needed; we review notes before publishing them.
Explore commentary across the portal →Published reader notes
0No published reader notes yet. You can start the evidence-led discussion above.
Prefer a private correction or response? Contact the newsroom.
