People search Dropbox data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 7 Dropbox-linked incidents, with headline counts up to 68.7M+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why Dropbox breach history matters
Dropbox operates in Technology (United States). Across indexed rows, recurring themes include credential theft and social engineering. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2024 — emails, hashed passwords, API keys
Cataloged incident. Dropbox discovered unauthorized access to Dropbox Sign (formerly HelloSign) production environment. A threat actor compromised a back-end service account and accessed the customer database. Exposed: email addresses, usernames, phone numbers, hashed passwords, API keys, OAuth tokens, MFA data. Document contents and payment info were not accessed. Exposed categories include Emails, usernames, phone numbers, hashed passwords, API keys, OAuth tokens. No attested victim count is published for this row yet. See the dropbox-sign2024 and canonical BreachHistory entry.
2016 — — Dropbox: User credentials were stolen in a 2012 hack, but…
Cataloged incident. Aug 2016. User credentials were stolen in a 2012 hack, but the number affected has only just come to light. BreachHistory cites approximately 68.7M+ affected records in this row. See the dropbox2016 and canonical BreachHistory entry.
2012 — 68.6M accounts
Cataloged incident. Email addresses and hashed passwords (SHA1, bcrypt) stolen. Full scope revealed in 2016 when 5GB database circulated on dark web. Forced password resets for pre-mid-2012 accounts. Exposed categories include Email addresses, Passwords (hashed), Addresses. BreachHistory cites approximately 68.6M+ affected records in this row. See the db2012 and canonical BreachHistory entry.
2012 — 2012
Cataloged incident. Websites stolen from other websites used to sign into a small number of Dropbox accounts. The hack was mainly used to send spam to users. No attested victim count is published for this row yet. See the dropbox2012 and canonical BreachHistory entry.
2012 — — Dropbox: Hacked, 30K records
Cataloged incident. Data breach reported to Have I Been Pwned or similar sources. Further technical details not publicly disclosed. BreachHistory cites approximately 30K+ affected records in this row. See the dropboxu and canonical BreachHistory entry.
2012 — — Dropbox: Hacking, 68,648,009 records
Cataloged incident. Data breach reported. web organization. Method: hacked. Source: Wikipedia List of data breaches. Exposed categories include Personal and demographic data. BreachHistory cites approximately 68.6M+ affected records in this row. See the dropbox2012-68648009-wiki2 and canonical BreachHistory entry.
2011 — — Dropbox: At least one customer reported a glitch that…
Cataloged incident. At least one customer reported a glitch that allowed users to log into the accounts of other users without using a valid password. The bug that affected the password authentication mechanism was active from 1:54pm to 5:46pm Pacific time on June 19, 2011.UPDATE (6/30/2011): It appears that an intrusion created the security issue that allowed people to log into user accounts without using a password. Someone logged into multiple customer accounts without authorization on June 19, 2011. Fewer than Exposed categories include Personal information. No attested victim count is published for this row yet. See the dropbox2011 and canonical BreachHistory entry.
Patterns and analysis
- Credential theft and social engineering — appears across multiple Dropbox catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Review OAuth app permissions and revoke unused third-party integrations.
- Step 5: Bookmark the Dropbox company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/dropbox · Latest: dropbox-sign2024.
Sources: BreachHistory catalog (7 rows for Dropbox), company and regulator disclosures cited in individual breach records.