This paper presents a large-scale empirical study using the AIDev dataset to systematically characterize security code smells in agent-generated pull requests (PRs), finding that human collaborators are responsible for introducing 67.6% of genuine leaked secrets within these agent-assisted workflows.
Abstract
The increasing adoption of autonomous coding agents accelerates software development but also introduces scoped security risks within high-impact file paths that can outpace traditional human review capacity. While prior research has primarily evaluated these systems in terms of functional correctness and productivity, this paper presents a large-scale empirical study using the AIDev dataset to systematically characterize security code smells in agent-generated pull requests (PRs). Through a combination of a validated LLM-as-a-judge framework and manual qualitative analysis, we identify and classify security misconfigurations across 16,112 file changes spanning 4,022 pull requests. Our results reveal that 38.9% of agent-generated PRs contain at least one security smell, with supply chain integrity issues accounting for 82.3% of all detected security smells. Furthermore, hard-coded credentials constitute 99.6% of all critical-severity security smells. Crucially, we find that human collaborators are responsible for introducing 67.6% of genuine leaked secrets within these agent-assisted workflows, while existing automated and human review processes fail to detect 81.1% of these credentials prior to integration. These findings highlight substantial security risks in agent-assisted software development workflows and suggest a potential reduction in developer vigilance. They also underscore the urgent need for context-aware security guardrails implemented directly at the point of human-AI collaboration.
This evidence-centered structured survey synthesizes representative work available through May 31, 2026 across software engineering tasks, software security tasks, adaptation mechanisms, artifact granularity, and evaluation design and introduces an assurance framework that separates functional correctness, security, op...
Wei Lin, Tao Zhou, Zhaofei Xie et al.· 0 citations
It is proved that current AI coding assistants do not produce secure-by-default applications, dictating that enterprise deployments must transition from single-shot prompt engineering to continuous, standards-driven verification pipelines.
An Information Flow Graph monitor is introduced that analyzes structural security regressions using control-flow and data-flow graph diffs alongside raw code diffs and suggests that untrained structural monitors provide a practical and auditable path toward democratizing deployment safety for organizations seeking trus...
Preeti Ravindra, Rahul Tiwari, Vincent Wolowski· arXiv.org· 1 citation· ⚡1
The risk is not tied to any particular model but rather to the task category, and organizations should ask not which tool to trust, but instead whether LLM-generated automation code should be deployed without review.
Shanna M. Kahn, John D. Hastings· arXiv.org· 0 citations
This study revisits how MCP security is measured and presents MCPZoo, the largest collection of MCP servers for dynamic analysis to date, and conducts the first ecosystem-scale measurement of MCP servers and the scanners that analyze them.
Pei Chen, Baichao An, Mengying Wu et al.· arXiv.org· 6 citations
Stealth, the discipline of achieving an objective without revealing your presence, capabilities, or collected intelligence, is what separates sophisticated operators from detectable ones. Elite security researchers and advanced persistent threats achieve their objectives unnoticed; autonomous agents increasingly inheri...
Ads Dawson, A. Wood· 0 citations
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.