Study: Separating self-critique from external proposals improves red-team attack success rate
Start here
A study published on arXiv on October 26, 2026 proposes a role-separated red-teaming method: the target conversation is responsible for self-critique, while an external model proposes attack proposals. The researchers found that the target conversation's self-critique is based on the real-time execution context, including observations, constraints, and available reasoning; removing reasoning reduces the downstream attack success rate by 6% to 17%; self-proposal performs markedly worse, because awareness of the adversarial objective induces explicit refusals and non-refusal-style deliberate underperformance. The method achieves an overall attack success rate of 63.2% on DTAP-BENCH, markedly higher than the baselines.
Generated by AI from reports · Updated 16 days ago
Attention and developments
Attention, hourly
Now 28, 0% in 24 hours·Peak 28 (Nov 7 01:00)
Related research
This event's paper
- The Target Agent Is Its Own Best Critic but a Poor Proposer: Self-Improved Red Teaming
arXiv · 2026-10-26 · Deep reading
Progress timeline
- XiaohongshuXiaohongshu · Liu Dongrui (Shanghai AI Lab)· DiscussionUIUC: Self-Improving Red Teaming(opens the original post in a new tab)
- arXivThe target agent is its own best critic but a poor proposer: self-improving red teaming
Researchers found that in automated red teaming, target-session self-critique is effective while self-proposal is poor, and on this basis proposed a role-separated red teaming method that achieved 63.2% overall attack success rate (ASR) on DTAP-BENCH, clearly higher than the baseline. Self-critique is more effective because it is based on the target session's real-time execution context, including observations, constraints and available reasoning; removing reasoning reduces downstream attack success rate by 6%-17%. Self-proposal performs clearly worse because awareness of the adversarial goal induces explicit refusals and non-refusal deliberate sandbagging. The role-separated method has the target session diagnose the reasons for attack failure, while a separately instantiated attacker generates the next proposal; it was validated on DTAP-BENCH covering the Telecom, Workflow, CRM and Code domains, under both direct misuse and indirect threat threat models and across multiple Agent frameworks. The paper concludes that effective automated red teaming depends not only on model capability and search strategy, but also on how execution context and adversarial responsibility are allocated across different model sessions.
Related discussion
- Older than 72 hours · Not included in the 72-hour figures
- XiaohongshuXiaohongshu · Liu Dongrui (Shanghai AI Lab)UIUC: Self-Improving Red Teaming(opens the original post in a new tab)
Attention trend
New sources per day
- Nov 4: 1 new sources (0 outlets, 1 accounts)
- Nov 5: 0 new sources (0 outlets, 0 accounts)
- Nov 6: 0 new sources (0 outlets, 0 accounts)
- Nov 7: 0 new sources (0 outlets, 0 accounts)
- Nov 8: 0 new sources (0 outlets, 0 accounts)
- Nov 9: 0 new sources (0 outlets, 0 accounts)
- Nov 10: 0 new sources (0 outlets, 0 accounts)
- Nov 11: 0 new sources (0 outlets, 0 accounts)
- Nov 12: 0 new sources (0 outlets, 0 accounts)
- Nov 13: 0 new sources (0 outlets, 0 accounts)
- Nov 14: 0 new sources (0 outlets, 0 accounts)