Dropbox (2022): what the sources say about the cloud incident
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
Dropbox disclosed the incident on 1 Nov 2022. What was exposed, as the sources state it: The company stated that the threat actor copied 130 code repositories containing some credentials (primarily API keys) and a few thousand names and email addresses; no customer content, passwords or payment information was accessed.
Open the ledger · Report a correction
- Disclosed
- 1 Nov 2022
- Incident window
- October 2022 (GitHub alert 2022-10-14, activity began the previous day)
- Cloud or provider
- GitHub
- What was exposed
- The company stated that the threat actor copied 130 code repositories containing some credentials (primarily API keys) and a few thousand names and email addresses; no customer content, passwords or payment information was accessed.
- How access was gained
- The company stated that employees received phishing emails impersonating a CI service, and that a fake login page collected GitHub credentials and a one-time code, giving the threat actor access to one GitHub organization.
- Access path
- Stolen user credentials and session tokens; also Leaked access keys and secrets
- Kind of control that addresses it
- require phishing-resistant authentication (WebAuthn) for source-control accounts and keep API keys out of repositories
In the words of the source
“These legitimate-looking emails directed employees to visit a fake CircleCI login page, enter their GitHub username and password, and then use their hardware authentication key to pass a One Time Password (OTP) to the malicious site.” (company statement, A recent phishing campaign targeting Dropbox)
Primary sources
- company statement: A recent phishing campaign targeting Dropbox, dated 1 Nov 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
- A recent phishing campaign targeting Dropbox, read 16 Nov 2026
Last reviewed 16 Nov 2026.