Backend
NameTrap: Steering AI Coding Agents Toward Security Vulnerabilities via Variable Names
arXiv cs.CR0 views
arXiv:2610.34253v1 Announce Type: new Abstract: AI coding agents routinely clone repositories, install packages, and read source code obtained from the Web, so publicly hosted code becomes part of the context that shapes the code they write. We show that this Web-borne context can be weaponized without any explicit instruction. We present NameTrap, a source-code poisoning attack that only renames identifiers in third-party Python files to steer AI coding agents toward attacker-targeted Common Weakness Enumeration (CWE) vulnerabilities. An attacker-side coding agent iteratively aligns identifiers with a CWE-specific naming convention and confirms through local probe completions that the renamed file elicits the target weakness, while the released bait contains neither instructions nor vulnerable statements. We evaluate NameTrap across six AI coding agents, ten underlying language models, and four vulnerability categories: CWE-78, CWE-79, CWE-327, and CWE-502. Starting from files whose clean versions never yield the targeted CWE, identifier-level manipulation achieves overall attack success rates of 22.5\% to 56.0\% across the six agents, reaching 75.0\% for certain agent--model configurations, and substantially outperforms random renaming, neutral renaming, and the prior identifier-poisoning attack XOXO. The attack remains effective under Traditional Chinese prompts and transfers across models, while a security-reminder defense fails to consistently prevent vulnerability introduction. Moreover, three AI-based security analyzers and four static analyzers report none of the targeted weaknesses in the poisoned files. These findings expose an overlooked attack surface of agents that consume Web content: seemingly harmless variable names in untrusted, Web-hosted code can compromise the security of downstream software.
Source:https://arxiv.org/abs/2610.34253PreviousHNSecW: A Logarithmic-Time MPC Protocol for Approximate Nearest Neighbor SearchNextRepairing Broken Access Control in Web Applications with LLMs: An Empirical Benchmark Study
Related posts
I Had a Perfect Sprint Board. 18 AI Subagents Still Wrecked the Repo.
0dev.to GitHub
What Is Attribution? AI Music Needs a Trail Back to the People Who Made the Work
0dev.to News
A Free Google Alerts Alternative: Monitoring Global News With the GDELT DOC API
0dev.to News
Butter Scraped Over Too Much Bread
0dev.to Discuss
From Six Seven to Six Zeros to What Next?
0dev.to Discuss
When a document assistant refuses: quota, context, and the missing model call
0dev.to C#