# AWS data breach: incidents in the ledger that involve AWS

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

Two ledger incidents name AWS in their primary source: the July 2025 Amazon Q Developer extension bulletin (AWS-2025-015) and the Salesloft Drift intrusion, whose summary says the actor reached Drift's AWS environment between March 22 and September 5, 2025. Capital One's sources describe a public cloud without naming AWS. Read 16 Nov 2026.

## AWS's own bulletin covers the Amazon Q Developer extension

AWS security bulletin AWS-2025-015, first dated July 23, 2025, concerns the Amazon Q Developer for Visual Studio Code extension (CVE-2025-8217). AWS wrote that the extension had an inappropriately scoped GitHub token in its CodeBuild configuration, and that with that token a threat actor committed malicious code to the extension's open-source repository, where it was automatically included in a release (AWS, read 16 Nov 2026).

AWS wrote that it revoked and replaced the credentials, removed the malicious code and released version 1.85.0. It also wrote that the code, distributed in version 1.84.0, was unsuccessful in executing because of a syntax error, so it made no changes to any services or customer environments. The bulletin adds that the code remains present in existing 1.84.0 installations, and tells customers to remove them and update.

The bulletin describes a build-pipeline token, not a flaw in an AWS data service. The ledger classes it as over-permissioned-identity.

## Salesloft's investigation summary places an actor in Drift's AWS environment

Salesloft's trust page lists an intrusion timeline running from March 22, 2025 to September 5, 2025. It says the actor used Salesloft GitHub personal access tokens for reconnaissance and secret enumeration, then accessed Drift's AWS environment and obtained OAuth tokens for Drift customers' technology integrations. It says the actor then used those tokens to access data through Drift integrations (Salesloft, read 16 Nov 2026).

Among the remediation steps the page lists are an AWS lockdown covering security group and network ACL analysis, IAM role and policy review, container security, and logging and monitoring improvements. The page also says credentials such as OAuth tokens, employee passwords and application secrets were rotated, and that privileges were limited to the lowest levels necessary. The AWS environment here belonged to a customer of AWS; the page does not state that any AWS service failed.

## Where the sources name no provider

Several ledger incidents involve a cloud environment that the primary sources do not name, so they cannot be listed as AWS incidents. Capital One's 2019 statement and the OCC's 2020 consent order refer to the cloud operating environment and the public cloud without naming the provider. AT&T, Live Nation and Advance Auto Parts describe a third-party cloud platform or database environment without naming it. This page lists none of them as AWS incidents because no source read states it.

| Incident | Primary source | Provider named in source | Access path in the ledger |
| --- | --- | --- | --- |
| Amazon Q Developer extension, 2025 | AWS security bulletin | AWS | over-permissioned-identity |
| Salesloft Drift, 2025 | Salesloft trust page | AWS | leaked-access-key |
| Capital One, 2019 | Company page and OCC order | No | not public |
| AT&T, Live Nation, Advance Auto Parts, 2024 | SEC Form 8-K filings | No | third-party-access |

## No AWS service breach found

On 16 Nov 2026 the ledger holds no incident in which AWS stated that an outside party gained access to AWS's own infrastructure or to a service's customer data through a flaw in an AWS service. The AWS-related entries above involve a code-signing pipeline token and a customer's use of AWS. This is a statement about the sources read on that date, not a claim that none exists.

## Related pages

- [Cloud Data Breaches: What Was Exposed, As Stated](/cloud-data-breaches/)
- [Recent Cloud Security Breaches, 2025 and 2026](/recent-cloud-security-breaches/)
- [Cloud Misconfiguration Breaches in the Ledger](/cloud-misconfiguration-breaches/)
- [All of them](/guides/)

## Sources

- AWS security bulletin AWS-2025-015: https://aws.amazon.com/security/security-bulletins/AWS-2025-015/ (read 16 Nov 2026)
- Salesloft, Drift security update: https://trust.salesloft.com/?uid=Drift+Security+Update (read 16 Nov 2026)
- Capital One, Information on the Capital One cyber incident: https://www.capitalone.com/digital/facts2019/ (read 16 Nov 2026)
- OCC consent order, AA-EC-20-49: https://www.occ.gov/static/enforcement-actions/ea2020-036.pdf (read 16 Nov 2026)
- AT&T Inc., Form 8-K, Item 1.05: https://www.sec.gov/Archives/edgar/data/732717/000073271724000046/t-20240506.htm (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudsecuritybreaches.com/aws-data-breach/
