Skip to content
Cloud Security Breaches

Amazon Web Services (2025): what the sources say about the cloud incident

Amazon Web Services disclosed the incident on 23 Jul 2025. What was exposed, as the sources state it: Malicious code was committed to the open-source repository of the Amazon Q Developer for VS Code extension and distributed in version 1.84.0; AWS stated it was unsuccessful in executing and made no changes to services or customer environments.

Open the ledger · Report a correction

Disclosed
23 Jul 2025
Incident window
not public
Cloud or provider
AWS
What was exposed
Malicious code was committed to the open-source repository of the Amazon Q Developer for VS Code extension and distributed in version 1.84.0; AWS stated it was unsuccessful in executing and made no changes to services or customer environments
How access was gained
The bulletin says the extension had an inappropriately scoped GitHub token in its CodeBuild configuration, and with that token the threat actor committed malicious code.
Access path
Over-permissioned identities; also Leaked access keys and secrets
Kind of control that addresses it
give build-system tokens the narrowest repository permissions and require review before any commit can enter a release

In the words of the source

“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.” (provider post mortem, Security Update for Amazon Q Developer Extension for Visual Studio Code (Version #1.84), AWS-2025-015)

Primary sources

If a field is wrong or a newer primary source exists, write to the editor with the entry name in the subject.

Sources

  1. Security Update for Amazon Q Developer Extension for Visual Studio Code (Version #1.84), AWS-2025-015, read 16 Nov 2026

Last reviewed 16 Nov 2026.