# Drizly (2022): what the sources say about the cloud incident

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

Drizly disclosed the incident on 24 Oct 2022. What was exposed, as the sources state it: 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.

- **Disclosed:** 24 Oct 2022
- **Incident window:** April 2018 (executive granted GitHub repository access) and early July 2020 (intrusion)
- **Cloud or provider:** AWS
- **What was exposed:** 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.
- **How access was gained:** 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.
- **Access path:** [Stolen user credentials and session tokens](/access-paths/stolen-user-credentials/); also [Leaked access keys and secrets](/access-paths/leaked-access-key/)
- **Kind of control that addresses it:** require MFA on source-control accounts, never store cloud credentials in repositories, and limit employee access to personal data

## In the words of the source

“The intruder used the compromised credentials from Drizly’s GitHub repositories to modify the company’s AWS security settings.” (regulator filing, [FTC complaint, Drizly LLC](https://www.ftc.gov/system/files/ftc_gov/pdf/202-3185-Drizly-Complaint.pdf))

## Primary sources

- regulator filing: [FTC complaint, Drizly LLC](https://www.ftc.gov/system/files/ftc_gov/pdf/202-3185-Drizly-Complaint.pdf), dated 24 Oct 2022

If a field is wrong or a newer primary source exists, [write to the editor](mailto:editor@cloudsecuritybreaches.com?subject=Correction%3A%20Drizly%20(drizly-ftc-2022)) with the entry name in the subject.

## Related pages

- [Microsoft (misconfigured storage endpoint) 2022: public st](/incidents/microsoft-misconfigured-endpoint-2022/)
- [Uber 2022: stolen user credentials and session tokens](/incidents/uber-2022/)
- [GitHub users (phishing campaign reported by GitHub) 2022: ](/incidents/github-circleci-phishing-2022/)

## Sources

- FTC complaint, Drizly LLC: https://www.ftc.gov/system/files/ftc_gov/pdf/202-3185-Drizly-Complaint.pdf (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudsecuritybreaches.com/incidents/drizly-ftc-2022/
