Twilio (2022): what the sources say about the cloud incident
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
Twilio disclosed the incident on 7 Aug 2022. What was exposed, as the sources state it: The company stated that 163 Twilio customers, out of a customer base of over 270,000, had data accessed without authorization, and that 93 individual Authy users, out of approximately 75 million, had additional devices registered to their accounts.
Open the ledger · Report a correction
- Disclosed
- 7 Aug 2022
- Incident window
- August 2022 (company became aware 2022-08-04)
- Cloud or provider
- Twilio
- What was exposed
- The company stated that 163 Twilio customers, out of a customer base of over 270,000, had data accessed without authorization, and that 93 individual Authy users, out of approximately 75 million, had additional devices registered to their accounts.
- How access was gained
- The company stated that text messages sent to current and former employees led some of them to a page impersonating the Twilio sign-in page, and that the attackers used the stolen credentials to reach internal systems.
- Access path
- Stolen user credentials and session tokens
- Kind of control that addresses it
- require phishing-resistant MFA (hardware-bound credentials) for every workforce identity with access to customer data systems
In the words of the source
“The attackers then used the stolen credentials to gain access to some of our internal systems, where they were able to access certain customer data.” (company statement, Incident Report: Employee and Customer Account Compromise)
Primary sources
- company statement: Incident Report: Employee and Customer Account Compromise, dated 7 Aug 2022
If a field is wrong or a newer primary source exists, write to the editor with the entry name in the subject.
Related pages
Sources
- Incident Report: Employee and Customer Account Compromise, read 16 Nov 2026
Last reviewed 16 Nov 2026.