Malicious code shipped in an Amazon Q Developer release, but AWS says it did not execute

A malicious change reached a release

In July 2025, an attacker used an inappropriately scoped GitHub token to commit malicious code to the open-source repository for Amazon Q Developer’s Visual Studio Code extension. The code shipped in version 1.84.0. It was designed to invoke Q CLI with instructions to remove local files and cloud resources, turning a compromised developer-tool release into a potential destructive action.

AWS says the payload never executed because it contained a syntax error. The company found no impact to AWS services or customer environments. AWS published security bulletin AWS-2025-015 on July 23; the incident is also tracked as CVE-2025-8217 and in the repository as GHSA-7g7f-ff96-5gcw. JFrog’s analysis describes how the code entered the extension.

Why the near miss matters

No customer wipe was confirmed, but malicious code had already crossed the boundary into a published extension. A syntax error happened to stop this payload; a future compromised release might not fail in the same way. The important failure was excessive access to the repository and the path from a source change to a shipped artifact.

• Restrict build tokens to the smallest necessary permissions and use short-lived credentials
• Require independent review of release workflow and startup-code changes
• Scan the packaged extension and use staged releases that can be rolled back quickly