Skip to content
Cloud Security Breaches

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

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.

Open the ledger · Report a correction

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; also Leaked access keys and secrets
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)

Primary sources

If a field is wrong or a newer primary source exists, write to the editor with the entry name in the subject.

Sources

  1. FTC complaint, Drizly LLC, read 16 Nov 2026

Last reviewed 16 Nov 2026.