IDE extension

The Amazon Q Developer for VS Code Supply Chain Attack

Updated 5 Oct 2026 · Incident date 17 Jul 2025

Amazon Q Developer for VS Code 1.84.0 carried injected text that told its AI assistant to erase files and cloud resources, released 17 July 2025.

An attacker added malicious code to the extension's repository. AWS fixed the problem in version 1.85.0 and removed 1.84.0 from its distribution channels.

What happened

An attacker used an overly broad GitHub token in the CodeBuild configuration. The token let the attacker inject a prompt that told the AI assistant to wipe a system.

  • 13 July 2025: the attacker plants the code through a pull request from a random account.
  • 17 July 2025: Amazon publishes version 1.84.0 with the code inside.
  • 23 July 2025: researchers report the problem to Amazon.
  • 24 July 2025: AWS releases version 1.85.0.
  • 25 July 2025: the story becomes public.

AWS states that the code did not run because of a syntax error.

Affected versions

  • Affected: Amazon Q Developer for VS Code 1.84.0.
  • Fixed: 1.85.0, released 24 July 2025.
  • Last clean line before the attack: 1.83.x.
  • Advisory GHSA-7g7f-ff96-5gcw tracks it as CVE-2025-8217.

Indicators of compromise

  • Extension version 1.84.0 installed in VS Code.
  • SHA256 of the 1.84.0 package, as published by AWS: 47f7840ecab6312d2733e1274c513050405886c70f2037fb2f1e9099872b0464.
  • Prompt text in the extension code that tells an assistant to "clear a system to a near-factory state" and to delete file-system and cloud resources.

How to check

List your installed extensions and look for Amazon Q. Version 1.84.0 is the bad one.

code --list-extensions --show-versions | grep -i amazon

If you keep the downloaded VSIX file, compare its hash with the AWS value above.

shasum -a 256 path/to/extension.vsix

What to do now

  1. Open the Extensions panel in VS Code and update Amazon Q Developer to version 1.85.0 or later.
  2. Check that the installed version is not 1.84.0.
  3. If 1.84.0 was installed, look for unexpected file deletions and unexpected activity in your cloud accounts.
  4. Pin extension versions in managed environments.

Frequently asked questions

How many people had the extension?

BleepingComputer reports nearly one million installs on the VS Code marketplace at the time.

Do all sources agree that the code did not run?

No. BleepingComputer notes that some experts said the code ran without causing harm. The sources do not settle this point.

How severe is the issue?

The GitHub advisory gives a CVSS v3.1 score of 4.0 (Moderate). The score is low because the code did not run.

Sources

  1. github.com/aws/aws-toolkit-vscode/security/advisories/GHSA-7g7f-ff96-5gcw
  2. aws.amazon.com/security/security-bulletins/AWS-2025-015/
  3. bleepingcomputer.com/news/security/amazon-ai-coding-agent-hacked-to-inject-data-wiping-commands/

Send this page to the person who looks after AI at your company.

Email it

More supply chain attacks

All 172 attacks in the library · What is a supply chain attack? · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library