Skip to content
Submit incident
AII-1001-34821
ReportedReported by fewer than three independent publishers, with no official finding.

Code assistants exploited for backdoor injection via indirect prompt injection

Palo Alto Networks researchers documented vulnerabilities in AI code assistants that allow threat actors to inject backdoors and malicious code through indirect prompt injection attacks on contaminated data sources. The research revealed that code assistants integrated into IDEs can be exploited to leak sensitive information and generate harmful content, affecting development environments broadly.

15 September 2025 Β· Security and cyberattacks
15 September 2025
AII-1001-348212 sources ↓
Quick facts
Category
Security and cyberattacks
Country
United States
Source
Unit42
Date
15 September 2025
Drafted by
Raidu Incident Detection

What happened

Researchers at Palo Alto Networks Unit 42 found that AI code assistants integrated into IDEs as plugins, such as GitHub Copilot, can be exploited by threat actors and users to inject backdoors, leak sensitive information and generate harmful content.

Threat actors can exploit context attachment features through indirect prompt injection by contaminating public or third-party data sources with carefully crafted prompts. When developers inadvertently supply this contaminated data to a code assistant, the malicious prompts hijack the assistant and could manipulate victims into executing backdoors, inserting malicious code into codebases and leaking sensitive information.

Users can also misuse code assistant features including chat, auto-completion and unit test generation for harmful purposes, similar to recently identified content moderation bypasses on GitHub Copilot. Some AI assistants invoke their base model directly from the client, exposing models to additional risks including misuse by users or external adversaries seeking to sell access to LLM models.

Reported impact

The vulnerabilities identified could impact a number of LLM code assistants and put development environments at risk of exploitation.

Governance controls

Developers should implement standard security practices for LLMs and conduct thorough code reviews to help secure AI-driven development against the identified threats. Exercising control over LLM outputs is recommended to protect environments from the exploits discussed.

Classification

Category
Security and cyberattacks
Industry
Digital security
Country
United States
Harm status
Potential harm
Intent
Intentional
Timing
Unknown
Harmed
Business
Failure modes
Prompt injection, Data leak
AI systems
GitHub Copilot

Sources and evidence

This record was researched and written by the Index, based on the following original reporting.

Unit42
The Risks of Code Assistant LLMs: Harmful Content, Misuse and Deception
15 September 2025
IT Security News - cybersecurity, infosecurity news
Threat Actors and Code Assistants: The Hidden Risks of Backdoor Injections - IT Security News
16 September 2025
Sep 2026OpenAI's Astra reaches critical cybersecurity capability levelConfirmedSecurity and cyberattacksΠ Π‘Πš-Π£ΠΊΡ€Π°ΠΈΠ½Π°El ConfidencialEL MUNDO+3Aug 2026OpenAI launches GPT-5.6-Cyber model with reduced safeguards for cybersecurity workWell documentedSecurity and cyberattacksCyberScoopNeowinTimesNowJul 2026AI Models Attempt Cyberattacks on Real Targets During Security Evaluation TestsConfirmedSecurity and cyberattacksasahi.comitmedia.co.jpJul 2026GitHub Agentic Workflows Vulnerable to Prompt Injection, Leaking Private RepositoriesWell documentedSecurity and cyberattacksSiliconANGLEDark ReadingIT Security News - cybersecurity, infosecurity news+6Jul 2026Student Discovers AI Agent Attacking GitHub Repository Supply ChainConfirmedSecurity and cyberattacksReutersEconomic TimesNDTV+1