Skip to content
Cloud Security Breaches

Leaked access keys and secrets: 27 incidents in the ledger

A leaked access key is a long-lived key, token or secret that ended up somewhere it should not be, such as a code repository, a container image, a log or a public file, and was then used by someone other than its owner to call a cloud provider's interfaces or reach a service.

Open the ledger ยท All eight paths

How it works

Cloud providers issue long-lived credentials for programmatic access: a key pair for a user, a key file for a service account, or a shared access signature for a storage account. AWS documentation says access keys are long-term credentials that sign requests to its API and that its secret half can be retrieved only when the key is created. Microsoft's documentation says a leaked shared access signature can be used by anyone who obtains it. Google Cloud's documentation lists credential leakage as a risk of service account keys.

The credential carries no information about who holds it. Whoever presents a valid key is treated as its owner, from any network, until the key is deleted or expires. For that reason the providers' guidance, read 16 Nov 2026, favors temporary credentials that expire on their own and keeping keys out of application files, and Microsoft's guidance adds short expiry times and a revocation plan for tokens that must exist.

The incidents

DisclosedOrganizationCloudHow access was gained
2025-09-22GitHub (npm registry)GitHubGitHub stated that a self-replicating worm spread through compromised maintainer accounts by injecting malicious post-install scripts into popular packages.
2025-09-02CloudflareSalesforceThe company stated the threat actor obtained OAuth credentials associated with the Salesloft Drift chat agent's Salesforce integration, and used a stolen credential used by the Salesloft integration to log in to its Salesforce tenant.
2025-08-26Nx (Nrwl)GitHubThe post-mortem says attackers exploited a GitHub Actions injection vulnerability to steal the npm publishing token; the repository's workflow permissions were read and write.
2025-08-20Salesloft (Drift)AWSThe investigation summary says the threat actor accessed the Salesloft GitHub account (March to June 2025), then accessed Drift's AWS environment and obtained OAuth tokens for customers' integrations, and used them to access data via Drift integrations.
2025-07-23Amazon Web ServicesAWSThe bulletin says the extension had an inappropriately scoped GitHub token in its CodeBuild configuration, and with that token the threat actor committed malicious code.
2024-12-08BeyondTrustAmazon Web ServicesThe company stated a zero-day vulnerability of a third-party application was used to gain access to an online asset in a BeyondTrust AWS account, which allowed the threat actor to obtain an infrastructure API key that was then used against a separate AWS account that operated Remote Support infrastructure.
2024-05-01Dropboxnot publicThe company stated a third party gained access to an automated system configuration tool, compromised a back-end service account with privileges across the production environment, and reached the customer database; it answered how access was gained with a compromised access token.
2024-02-01CloudflareOktaThe company stated the actor used one access token and three service account credentials taken in the October 2023 Okta compromise that the company had failed to rotate.
2023-11-07Sumo LogicAWSThe customer notice says the activity used a compromised credential to access a Sumo Logic AWS account. How the credential was compromised is not public.
2023-09-18MicrosoftMicrosoft AzureMicrosoft stated an employee shared a URL for a blob store in a public GitHub repository, and the URL included an overly-permissive Shared Access Signature token for an internal storage account.
2023-08-30Sourcegraphnot publicThe company stated a malicious actor used a leaked site-admin access token, accidentally committed in a pull request, to raise an account to site-admin on Sourcegraph.com.
2023-08-16E-Commerce Enablers Pte. Ltd.AWSThe decision says an AWS access key with full administrative privileges was committed to a private GitHub repository on 4 June 2019, removed on 6 June but still viewable in the commit history, and not fully disabled when a replacement key was created. On 9 September 2020 a threat actor used it to reach the AWS environment, changed security settings to allow remote internet access to database instances and exfiltrated data. The company conjectured the key was found in the commit history.
2023-07-11MicrosoftMicrosoft 365Microsoft stated the actor used an acquired Microsoft account consumer signing key to forge tokens, and exploited a token validation issue so that enterprise mail accepted them. The post-mortem says the most probable mechanism for the key acquisition was a compromised engineer corporate account with access to a debugging environment holding a crash dump that contained the key.
2023-03-23GitHubGitHubThe company stated the exposure resulted from what it believes was an inadvertent publishing of private information.
2022-12-22LastPassnot publicThe company stated that an unknown threat actor accessed a cloud-based storage environment using information obtained from the August 2022 incident, and that credentials and keys obtained from another targeted employee were used to access and decrypt some storage volumes.
2022-12-19RedMart LimitedAWS and Alibaba CloudThe decision says a threat actor gained unauthorised access to the GitHub account of a member of the DevOps team, found a high-privilege key to the AWS environment in the repositories, used it to find a second key in a private S3 bucket, created an EC2 instance, and crossed a VPN link to the Alibaba cloud database. The database was neither encrypted nor password protected.
2022-11-01DropboxGitHubThe company stated that employees received phishing emails impersonating a CI service, and that a fake login page collected GitHub credentials and a one-time code, giving the threat actor access to one GitHub organization.
2022-10-24DrizlyAWSThe FTC complaint stated that in early July 2020 a malicious actor reused credentials from an unrelated breach to reach an executive's GitHub account, found AWS and database credentials stored in the company's GitHub repositories, and used them to change the company's AWS security settings and reach the production environment.
2022-09-15MyRepublic LimitedAWSThe decision says the Mobile Order Portal stored KYC documents in a bucket on AWS cloud storage, and the bucket's access key sat in the portal's source code. The external actor used the key to access the bucket. The company could not determine with certainty how the key was obtained but found it was disclosed in a portal page showing technical information and in a source repository open to all its developers.
2022-04-21GeniusU Pte. Ltd.GitHubThe decision says the likely cause was a compromise of a developer's GitHub password, which let the threat actor into the company's GitHub environment; database login credentials had been stored in the codebase there, so the actor reached and exfiltrated the database. The staging database held real personal data.
2022-04-15Heroku (Salesforce) and Travis CI OAuth tokensGitHubHeroku stated that initial access to its environment was obtained by using a compromised token for a Heroku machine account, after which stored customer GitHub integration OAuth tokens were downloaded; GitHub stated the tokens were then abused against GitHub.com.
2021-11-11Commeasure Pte Ltd (operates the RedDoorz booking platform)AWSThe decision says the threat actors most likely obtained an AWS access key embedded in an Android application package, created in 2015, last updated in January 2018, still downloadable from the Google Play Store, and marked as a test key although it could reach a live production database in Amazon RDS.
2021-09-21Sendtech Pte. Ltd.AWSThe decision says the cause was a compromised AWS access key created in 2015 and not rotated since. With it the attacker gained admin privileges, created another admin account and queried the buckets storing personal data. The company suspected the key could have been compromised through former or current employees but the decision does not confirm how.
2021-04-15CodecovCodecovThe company stated that an error in its Docker image creation process allowed the actor to extract the credential required to modify the Bash Uploader script, which was then altered to send CI environment variables to a third-party server.
2021-03-16MimecastMicrosoft 365The company stated the threat actor used the SolarWinds supply-chain compromise to gain access to part of its production grid environment, and from there accessed Mimecast-issued certificates and related connection information; the certificate was then used against a small number of customer Microsoft 365 tenants.
2020-07-11LiveAuctioneersAWSThe company's letter to the Washington Attorney General says a hacker breached one of its third-party software solutions and obtained a source control key, which gave access to its source repository, its cloud-based storage environment and its production database, then used internal users' credentials to download the user database.
2019-08-27ImpervaAWSThe company's follow-up post says an unauthorized use of an administrative API key in one of its production AWS accounts led to exposure of a database snapshot. It lists the steps as a snapshot created for testing, an internal compute instance accessible from the outside world that contained an AWS API key, compromise of that instance and theft of the key, and use of the key to access the snapshot.

The kind of control that addresses it

replace long-lived keys with short-lived credentials issued to the workload, and scan code, logs and files for secrets before they are published

Sources

  1. AWS IAM User Guide: manage access keys for IAM users, read 16 Nov 2026
  2. AWS IAM User Guide: temporary security credentials, read 16 Nov 2026
  3. Microsoft Learn: shared access signatures overview, read 16 Nov 2026
  4. Google Cloud: best practices for managing service account keys, read 16 Nov 2026

Last reviewed 16 Nov 2026.