# Twitter (2020): what the sources say about the cloud incident

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

Twitter disclosed the incident on 18 Jul 2020. What was exposed, as the sources state it: The company stated attackers targeted 130 Twitter accounts, tweeted from 45, accessed the direct message inbox of 36 and downloaded the Twitter Data of 7.

- **Disclosed:** 18 Jul 2020
- **Incident window:** July 15, 2020
- **Cloud or provider:** Twitter
- **What was exposed:** The company stated attackers targeted 130 Twitter accounts, tweeted from 45, accessed the direct message inbox of 36 and downloaded the Twitter Data of 7.
- **How access was gained:** The company says a phone spear phishing attack targeted a small number of employees; the attackers used the employees' credentials to access internal systems, including getting through two-factor protections, then used the credentials of employees with access to account support tools.
- **Access path:** [Stolen user credentials and session tokens](/access-paths/stolen-user-credentials/)
- **Kind of control that addresses it:** require phishing-resistant multi-factor authentication for every identity with access to internal support tools, with a second approver for account-changing actions

## In the words of the source

“The attackers successfully manipulated a small number of employees and used their credentials to access Twitter’s internal systems, including getting through our two-factor protections.” (company statement, [An update on our security incident (archived copy of the company blog, updated July 30, 2020)](https://web.archive.org/web/20200801/https://blog.twitter.com/en_us/topics/company/2020/an-update-on-our-security-incident))

## Primary sources

- company statement: [An update on our security incident (archived copy of the company blog, updated July 30, 2020)](https://web.archive.org/web/20200801/https://blog.twitter.com/en_us/topics/company/2020/an-update-on-our-security-incident), dated 30 Jul 2020

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

## Related pages

- [Blackbaud Inc. 2020: over-permissioned identities](/incidents/blackbaud-2020/)
- [LiveAuctioneers 2020: third-party access](/incidents/liveauctioneers-2020/)
- [Microsoft 2020: support database](/incidents/microsoft-support-database-2019/)

## Sources

- An update on our security incident (archived copy of the company blog, updated July 30, 2020): https://web.archive.org/web/20200801/https://blog.twitter.com/en_us/topics/company/2020/an-update-on-our-security-incident (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudsecuritybreaches.com/incidents/twitter-2020/
