Dropbox Watchdog

Search issues

Search the Dropbox Watchdog archive

All issues

Guiffre v. Dropbox: the class action over the 2024 Dropbox Sign breach

May 2024

HighStatus: Ongoing Hundreds of thousands (estimated) affectedProduct: Dropbox SignYear: 2024

Within weeks of the Dropbox Sign breach disclosure, users filed a proposed class action in California federal court alleging Dropbox failed to protect their data and was slow to notify them.

What happened

On 1 May 2024 Dropbox disclosed, in a blog post and an SEC Form 8-K, that an attacker had accessed the production environment of Dropbox Sign (its eSignature product, formerly HelloSign) and obtained customer data including emails, usernames, phone numbers, hashed passwords, API keys, OAuth tokens, and multi-factor authentication information. Notably, even people who had only received or signed a document through Sign — without ever creating an account — had their email addresses and names exposed.

Within weeks, plaintiffs filed a proposed class action, Guiffre v. Dropbox, Inc., No. 3:24-cv-02794, in the U.S. District Court for the Northern District of California. The complaint alleges that Dropbox failed to implement reasonable security measures to protect personally identifiable information and that the company learned of the unauthorized access on or about 24 April 2024 but did not notify affected users until early May, leaving them exposed to phishing, identity theft, and fraud in the interim. The suit seeks damages and injunctive relief requiring stronger security practices.

The case is one of several consumer claims arising from the Sign breach. As a proposed class action it must clear class-certification and pleading hurdles, and as with most data-breach litigation the path runs through motions over standing and concrete harm before any trial or settlement.

In 2025, U.S. District Judge Jeffrey S. White granted Dropbox's motion to compel arbitration in this case, ruling that plaintiffs who completed a signature request through Dropbox Sign had been shown a hyperlink to Dropbox's terms of service and, by clicking 'I agree' to sign the document, had agreed to be bound by those terms, including the arbitration clause and class-action waiver. The plaintiffs sought reconsideration, arguing the consent was not meaningful, but the court denied the motion — a ruling reported on 15 May 2026 — leaving the order intact and sending the breach claims to individual arbitration rather than a consolidated class action.

Impact

The litigation converts the Sign breach from a security event into an ongoing legal and financial liability and a recurring item in Dropbox's risk disclosures. It also spotlights a structural exposure of eSignature platforms: non-account 'recipients' whose data sits in the system without any direct relationship with the vendor. For users it underscores how a breach of a single acquired product (HelloSign/Sign) can sweep in people who never chose Dropbox at all.

Dropbox's Response / Official Position

Dropbox said it found no evidence the attacker accessed the contents of user documents or agreements, or their payment information, and that it had reset passwords, logged users out of Dropbox Sign, and rotated API keys and OAuth tokens. It said it was notifying affected users and had brought in outside forensic investigators and notified regulators and law enforcement. Dropbox has not, in its public statements, accepted the lawsuit's allegations of inadequate security.

Sources

Related guides

Spot an error, or have a source to add?
Report an error / suggest update

Related issues

9 sources
HighApproximately 5,000 accounts; files accessed in fewer than a third (about 1,500 by 9to5Mac's arithmetic)

The 2026 Lenovo ID sign-in flaw: ~5,000 Dropbox accounts entered without a Dropbox password

A flaw in how Lenovo verified account-holder email addresses let an attacker register a Lenovo ID on a victim's email, and Dropbox's Lenovo ID sign-in link then trusted that identity without ever asking for a Dropbox password — reaching roughly 5,000 accounts.

Security Incidents & Data BreachesCurrent / Ongoing Issues (2024–2026)
Read documentation

Across multiple years, attackers have built convincing fake Dropbox login pages — reached via PDF lures and redirect chains through trusted cloud storage — to harvest victims' real business email and Dropbox credentials.

Security Incidents & Data BreachesAccount Lockouts & Support Failures
Read documentation

In an 8-K filed May 26, 2026, Dropbox disclosed that co-founder Drew Houston would step back as CEO after 19 years, with the Board appointing Ashraf Alkarmi — its General Manager, Core — as Co-Chief Executive Officer effective that date, ahead of Alkarmi becoming sole CEO and Houston moving to executive chairman 'following a transition period.' The handoff arrives as AI upends the software era Dropbox grew up in and the company's revenue sits near flat.

Product Changes & User BacklashCurrent / Ongoing Issues (2024–2026)
Read documentation

Dropbox's Q1 and Q2 2026 results both kept total reported revenue growth under 1% year-over-year, the company refinanced debt and repurchased hundreds of millions of dollars in stock over the same six months, and the period closed with a co-CEO handoff, a new product chief, and a routine, tax-related insider stock disposition reported by the Motley Fool; in September three executives reported sales under Rule 10b5-1 plans adopted in June.

Pricing & Business PracticesCurrent / Ongoing Issues (2024–2026)
Read documentation