Hand-written summaryWorldwide
What happened
Attackers got a destructive instruction into version 1.84.0 of Amazon Q's coding extension. AWS says the code was shipped but did not run because of a mistake, and that no customer systems were changed.
Rated elevated: some people may need to check their accounts or update software. Why: a trusted tool shipped with a destructive instruction; AWS says it did not run and nothing was changed.
This incident may still be developing. Details can change.
Does this affect me?
Only if you installed version 1.84.0 of the Amazon Q extension.
Who may be affected: Anyone who installed version 1.84.0 of the Amazon Q Developer extension for VS Code.
You may be affected if
- You use AWS in a project or at work
- You installed or updated it during the period named in the report
You are probably not affected if
- You never installed the tool, package or update
- You do not build software
If you are unsure: Ask whoever maintains your software whether the affected tool is in use.
What to do now
- Check your editor's extensions. Remove version 1.84.0 of Amazon Q and update to 1.85.0 or later.
- Remove extensions you no longer use.
What to do next (24 to 48 hours)
- Review what else the tool is connected to.
- Check your build and deployment history for changes you do not recognise.
How to avoid this in future
- Pin versions and review changes before updating.
- Remove plugins and packages you no longer use.
- Limit what AI tools can read or change.
What we know, and what we do not
Stated by the source
- AWS says an over-powered token in the extension's build setup let an attacker add malicious code, which shipped in version 1.84.0.
- AWS says the code did not execute because of a syntax error, so it made no changes to services or customer environments.
- AWS cancelled and replaced the credentials, removed the code and released version 1.85.0.
Reported or claimed, not confirmed
- The Register reported the added text told an AI agent to delete files from the user's home directory and cloud resources. The intent was described as embarrassing AWS, based on an unverified claim by someone presenting as the attacker.
Still unclear
- Whether anyone's data was affected before the fix is not stated beyond AWS's account.
Official AWS bulletin AWS-2025-015.
Why it is on the radar
Worth learning from: 34/100
Low relevance because it matters to small teams and builders.
This is our own score for how useful an item is to everyday people and small teams. It is not an objective measure of how dangerous something is.
Sources
- AWS Security Bulletin: read the originalPublished 23 Jul 2025. Last retrieved 12 Nov 2026.
- Also reported by The RegisterPublished 24 Jul 2025.
- 23 Jul 2025 AWS Security Bulletin
- 24 Jul 2025 The Register
Learn more on CyberSafety.lol
Finished this one?
Add it to What I learned and earn 15 Trust. You can open your list from the badge at the bottom of the page.
This news feed monitors public reporting and official advisories. It does not capture every cyberattack worldwide.
Back to the security news feed