Back to the archive

The encyclopedia · Software & IT · Operational decision · 2016

Dropbox's 2012 breach exposed 68M accounts — disclosed as 'a small number'

In 2012, hackers stole 68M Dropbox credentials. Dropbox disclosed a partial breach. In 2016, the full 68M records appeared online. The delay damaged trust.

Dropbox · 2016-08

What happened

In 2012, hackers accessed Dropbox's systems and stole approximately 68 million user credentials — email addresses and hashed passwords. Dropbox disclosed a limited breach at the time, stating that a 'small number' of accounts had been compromised.

In August 2016, the full 68 million credentials appeared on a data-sharing site. Dropbox confirmed the data was authentic and acknowledged that the 2012 breach had been far larger than initially disclosed. The company forced password resets for all affected users.

The case was similar to the LinkedIn breach: a partial disclosure followed by the full truth emerging years later. Dropbox was criticized for not disclosing the full scope in 2012. The case illustrated how the pattern of 'disclose minimally, hope it goes away' is a recurring failure in the tech industry, and how the full truth always surfaces — usually at the worst possible time.

Why it happened

  • Dropbox disclosed a 'small number' of compromised accounts in 2012; the actual number was 68M.
  • The full 68M credentials appeared online in 2016.
  • Dropbox was criticized for not disclosing the full scope in 2012.
  • The pattern of minimal disclosure followed by full truth is a recurring tech industry failure.
What it cost68M accounts; 4-year disclosure delay; trust damagedcostly

The lesson

'Disclose minimally, hope it goes away' is a recurring tech failure. Dropbox said 'a small number'; it was 68M. The full truth always surfaces, usually at the worst time.

Aftermath

Dropbox reset all affected passwords and strengthened its security. The case contributed to the broader discussion about breach disclosure obligations in the tech industry.

Sources

spotted an error? The club wants to know.

Comments · 0

    Sign in to join the comments.

    More like this

    Somewhere, someone solved the problem this company failed at. 2nd Opinion →