AI failures · Security or operational lapse
Amazon (Q Developer): Over-Scoped GitHub Token Let an Attacker Add Malicious Code to the VS Code Extension
Verified Checked against its sources on 1 source quoted
- Where it happened
- International or several countries
- Organization
- Amazon Web Services (Amazon Q Developer extension)
- Date
- AWS bulletin AWS-2025-015, published July 23, 2025 and updated July 25, 2025; affected version 1.84.0
- Function
- AI coding assistant
- Work stage
- Extension build and release
- System
- Amazon Q Developer extension for Visual Studio Code
- Technology
- Conventional software (not AI)
- Type of failure
- Security or operational lapse
- Caught by
- Internal review
Summary
Amazon Web Services says that, in the course of investigating a related bulletin (AWS-2025-016), it determined that the Amazon Q Developer extension for Visual Studio Code had an inappropriately scoped GitHub token in its CodeBuild configuration. AWS says that with this token a threat actor committed malicious code into the extension's open-source repository and the code was automatically included in a release, version 1.84.0. AWS says it revoked and replaced the credentials, removed the malicious code and released version 1.85.0, and removed 1.84.0 from distribution channels. AWS says its inspection found the malicious code was distributed with the extension but was unsuccessful in executing because of a syntax error, so it did not change any services or customer environments, and that the code remains present in existing installations of 1.84.0.
Consequence
- AWS revoked and replaced the credentials, removed the malicious code and released version 1.85.0
- AWS removed version 1.84.0 from distribution channels so no further customers could install it
Who caught it Internal review
This is a security or operational lapse at an AI company or in an AI tool, not a failure of AI output or action. It is tracked here, kept separate from incident counts, and carries no lesson.
Key dates
- July 2025Event
- November 3, 2026Checked against sources
Developments are added when the record is reviewed. Next review: November 3, 2027.
Evidence
Each passage is quoted from its source. The record shows the date it was last checked.
-
With that access token, the threat actor was able to commit malicious code into the extension's open-source repository that was automatically included in a release.
Supports: what happened
was distributed with the extension but was unsuccessful in executing due to a syntax error.
Supports: limit
In the course of our investigation of AWS-2025-016 , we determined that Amazon Q Developer for VS Code Extension had an inappropriately scoped GitHub token in their CodeBuild configuration.
Supports: origin of the finding
After we identified this, we immediately revoked and replaced the credentials, removed the malicious code from the code base, and subsequently released Amazon Q Developer for VS Code Extension version 1.85.0.
Supports: response
This includes removing 1.84.0 from distribution channels so that no further customers can install it.
Supports: response
While the malicious code cannot execute, it is still present in existing installations of 1.84.0.
Supports: what remains
This prevented the malicious code from making changes to any services or customer environments.
Supports: AWS's statement of effect
Publication Date: 2025/07/23 6:00 PM PDT
Supports: date
Suggested citation. Eminence Scan, “Amazon (Q Developer): Over-Scoped GitHub Token Let an Attacker Add Malicious Code to the VS Code Extension”, Eminence Growth Solutions, last verified November 3, 2026, https://eminencegrowthsolutions.com/tools/eminence-scan/record/fail-146/.
Using our research: you may read and quote Eminence Scan with credit to “Eminence Scan, Eminence Growth Solutions” and a link; all other rights reserved. Terms: Using our research.
Spotted an error, or a development we have missed? Report a correction. How we check records: research methodology.
