Cloud breaches involving AWS: 19 in the ledger
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
19 incidents in the ledger involve AWS. The most common access path among them is leaked access keys and secrets. The earliest was disclosed in 2019 and the latest in 2026. Each incident links to its company statement, filing, court document or post-mortem.
Open the ledger · All providers
| Disclosed | Organization | Access path | What was exposed |
|---|---|---|---|
| 2026-01-08 | People Central Pte. Ltd. | Exposed network services and request paths | The PDPC decision states personal data of 95,000 employees of the company's clients was put at risk (including name, identity card number, salary, bank account number and address), plus 24,765 emergency contacts and children. The threat actor deleted databases and likely exfiltrated data, and data was found for sale on the dark web. |
| 2025-08-20 | Salesloft (Drift) | Leaked access keys and secrets | OAuth tokens for Drift customers' technology integrations, obtained from the Drift AWS environment; Salesloft GitHub repositories downloaded; environment variable secrets exfiltrated |
| 2025-07-23 | Amazon Web Services | Over-permissioned identities | 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 |
| 2024-04-22 | Payroll2U Pte. Ltd. | Stolen user credentials and session tokens | The PDPC decision states 81.95 GB of data was exfiltrated and posted on the dark web, including the personal data of 5,640 employees of a client: name, bank account number, salary, identity card number, address, date of birth and email. |
| 2023-11-07 | Sumo Logic | Leaked access keys and secrets | The company stated that, after investigation by its teams and third-party forensic experts, it found no proof of customer data impact. It advised customers to rotate API access keys and stored third-party credentials. |
| 2023-08-16 | E-Commerce Enablers Pte. Ltd. | Leaked access keys and secrets | The PDPC decision states customer data on virtual servers in an AWS environment was exfiltrated, with counts including 1,457,637 email addresses, 840,210 names, 447,076 mobile numbers, 299,381 bank account numbers and 378,531 partial credit card records. |
| 2023-06-16 | 1Health.io Inc. (formerly Vitagene, Inc.) | Public storage, databases and services | The FTC states nearly 2,400 health reports about consumers and raw genetic data of at least 227 consumers, sometimes accompanied by a first name, sat in publicly accessible buckets, unencrypted, according to the complaint. |
| 2022-10-24 | Drizly | Stolen user credentials and session tokens | The FTC complaint stated that Drizly's databases held personal information of more than 2.5 million consumers, that the intruder took a user table of more than 2.5 million records, and that the company hosted its production database on Amazon RDS, an AWS service. |
| 2022-09-15 | MyRepublic Limited | Leaked access keys and secrets | The PDPC decision states the personal data of 79,388 customers was accessed and exfiltrated: scanned copies of identity cards and work passes submitted as KYC documents and number portability documents. |
| 2022-07-14 | Crawfort Pte. Ltd. | Public storage, databases and services | The PDPC decision states the personal data of 5,421 customers was affected: images of identity cards, PDF loan contracts and income documents. |
| 2021-12-01 | A publicly traded wireless communications manufacturer (called Company-1 in the U.S. Attorney release) | Over-permissioned identities | The release says gigabytes of confidential data were downloaded from the company’s AWS and GitHub infrastructure and later used in an extortion attempt for millions of dollars. |
| 2021-11-11 | Commeasure Pte Ltd (operates the RedDoorz booking platform) | Leaked access keys and secrets | The PDPC decision states a database of 5,892,843 customer records (name, contact number, email, date of birth, hashed password and booking information) was accessed and exfiltrated; masked credit card numbers were not accessed. |
| 2021-09-21 | Sendtech Pte. Ltd. | Leaked access keys and secrets | The PDPC decision states the personal data of 64,196 customers and 3,401 contractors and the contractors' employees was accessed: for customers the email address, contact number, home address and last four digits of the card; for contractors and their employees a profile photo and copies of the NRIC or work permit. It states there was no evidence of data exfiltration. |
| 2020-08-26 | Cisco Systems | Retained access after departure or change | The press release says 456 virtual machines for the WebEx Teams application were deleted and over 16,000 WebEx Teams accounts were shut down for up to two weeks. It says the company spent approximately $1,400,000 in employee time and refunded over $1,000,000 to affected customers, and that no customer data was compromised. |
| 2020-07-22 | Twilio | Public storage, databases and services | A modified version (v1.20) of the TaskRouter JS SDK hosted on the company's content domain. The company stated it had no evidence that any customer data was accessed and that no malicious party had access to its internal systems, code or data; customers who downloaded v1.20 in the window were asked to replace it. |
| 2020-07-11 | LiveAuctioneers | Third-party access | The company's letter says 38,523 Washington residents were involved; the user database held names, email addresses (user names), MD5-hashed passwords, contact details, IP addresses used to create accounts and records of past sales transactions. It says no Social Security numbers or financial data were collected. |
| 2019-08-27 | Imperva | Leaked access keys and secrets | Elements of the Incapsula (Cloud WAF) customer database through September 15, 2017: email addresses and hashed and salted passwords, and for a subset of customers API keys and customer-provided SSL certificates. The company stated the exposure came from a database snapshot. |
| 2019-07-29 | Capital One | Exposed network services and request paths | The company stated the event affected approximately 100 million individuals in the United States and approximately 6 million in Canada. Credit card application data from 2005 through early 2019 (names, addresses, ZIP or postal codes, phone numbers, email addresses, dates of birth, self-reported income), portions of credit card customer data, about 140,000 Social Security numbers and about 80,000 linked bank account numbers of US secured credit card customers, and approximately 1 million Canadian Social Insurance Numbers. The company stated no credit card account numbers or log-in credentials were compromised. |
| 2019-06-28 | Online Buddies (Jack’d dating app) | Public storage, databases and services | The release says private photos (which may have included nude images), public photos and personal information (location, device ID, last login date, hashed password) were at risk of unauthorized access; counts not public. |
How access was gained, entry by entry
- People Central Pte. Ltd.: The decision says the company, a cloud-based HR software provider, had Remote Desktop Protocol access open to the internet without two-factor authentication on its AWS cloud servers, settings allowed inbound traffic from all IP addresses in the cloud environment, and SQL injection vulnerabilities were present with no web application firewall.
- Salesloft (Drift): The 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.
- Amazon Web Services: 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.
- Payroll2U Pte. Ltd.: The decision says a single compromised user account was used for Remote Desktop Protocol access to five servers in the company's AWS environment, and that investigators could not determine how the credentials were obtained. It lists no MFA for administrator accounts or accounts with access to personal data.
- Sumo Logic: The customer notice says the activity used a compromised credential to access a Sumo Logic AWS account. How the credential was compromised is not public.
- E-Commerce Enablers Pte. Ltd.: The 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.
- 1Health.io Inc. (formerly Vitagene, Inc.): The FTC press release says the company stored the data in publicly accessible buckets on AWS cloud storage, did not encrypt it, restrict access to it, log or monitor access to it, or inventory it, and that it was warned at least three times over a two-year period before investigating after a security researcher contacted it in June 2019.
- Drizly: The 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.
- MyRepublic Limited: The 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.
- Crawfort Pte. Ltd.: The decision says the company opened an S3 server port in its AWS environment for one week during a data migration, and that the S3 bucket holding the data was publicly accessible due to a misconfiguration. It states the threat actor gained access to the public bucket in that period.
- A publicly traded wireless communications manufacturer (called Company-1 in the U.S. Attorney release): The release says an employee who was a senior developer held credentials for the company’s AWS and GitHub servers and repeatedly misused his administrative access to download the data; the company’s own account of an outside intruder was, the release says, false.
- Commeasure Pte Ltd (operates the RedDoorz booking platform): The 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.
- Sendtech Pte. Ltd.: The 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.
- Cisco Systems: The Department of Justice says that under the plea agreement an individual who had worked for Cisco and resigned in approximately April 2018 admitted intentionally accessing Cisco's cloud infrastructure hosted by Amazon Web Services without permission on September 24, 2018, and deployed code from a Google Cloud Project account that deleted the virtual machines.
- Twilio: The company's incident report says a misconfiguration in the S3 bucket hosting the library let a bad actor inject code, and that the access policy for the path storing the SDK allowed anybody on the Internet to read and write to that path.
- LiveAuctioneers: The 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.
- Imperva: The 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.
- Capital One: The company stated that a highly sophisticated individual was able to exploit a specific configuration vulnerability in its infrastructure and that the issue was not specific to the cloud. The OCC consent order finds the bank failed to establish appropriate risk management for its cloud operating environment, including network security controls.
- Online Buddies (Jack’d dating app): The New York Attorney General’s investigation confirmed the company failed to secure user photos stored in an AWS S3 storage service, and left app interfaces to backend data unsecured.
Related pages
Sources
- People Central Pte. Ltd., read 16 Nov 2026
- Salesloft (Drift), read 16 Nov 2026
- Amazon Web Services, read 16 Nov 2026
- Payroll2U Pte. Ltd., read 16 Nov 2026
- Sumo Logic, read 16 Nov 2026
- E-Commerce Enablers Pte. Ltd., read 16 Nov 2026
Last reviewed 16 Nov 2026.