Skip to content
cisonews.net

Incident · 8-K Item 1.05

Dropbox reports unauthorized access to the Dropbox Sign production environment

Compiled from public records. Updated 2026-11-10. By the cisonews.net Desk.

Dropbox, Inc. disclosed to the SEC in a Form 8-K dated May 1, 2024 that it learned on April 24, 2024 of unauthorized access to the production environment of Dropbox Sign, formerly HelloSign. The actor reached data tied to all Dropbox Sign users, including emails and usernames, and more for subsets of users; the filing gives no total count of affected people.

Entries like this one, in Wednesday’s docket

Wednesdays

Unsubscribe any time.

The company's notice, filed with the 8-K as an exhibit, explains how. A third party reached a Dropbox Sign automated system configuration tool and compromised a service account, then used that access to reach the customer database. People who had only received or signed a document through Dropbox Sign, without an account, had their email addresses and names exposed. Dropbox reset passwords, logged users out of their devices and began rotating every API key and OAuth token.

What happened at Dropbox Sign, and when?

The filing says the company became aware of the access on April 24, 2024. It then started its incident response process to investigate, contain and remediate.

Dropbox also reports that it engaged outside forensic investigators and has notified law enforcement. It states that it is notifying regulators and users where personal information was accessed.

What did the Dropbox Sign breach expose?

For some users the access went beyond contact details and settings. The filing does not say how many users fall into those subsets.

Dropbox says it found no evidence that the contents of accounts or payment details were reached. It also believes the incident stayed within Dropbox Sign.

How did the attacker get into Dropbox Sign?

The way in was a machine account, not a person's login. Dropbox says a third party gained access to a Dropbox Sign automated system configuration tool. The actor compromised a service account in Sign's back end, the kind of non-human account that runs applications and automated services. That account had privileges to take a range of actions in Sign's production environment.

Dropbox also says Sign's infrastructure is largely separate from its other services, which is why it believes the rest of Dropbox was not affected. The notice does not say how the service account was compromised. The guide to vendor and cloud tenant breaches sets this entry point beside others in the log.

What did Dropbox Sign users have to do?

Dropbox's notice told each group of users what to change. Every user's password was expired, and the next login sends a reset email. API customers had to make a new API key, configure it and delete the old one. Until they did, only signature requests and signing kept working. Users with an authenticator app for multi-factor authentication had to delete the entry and set it up again; SMS users had nothing to do.

UserWhat was exposedWhat to do
Dropbox Sign account holderEmail, username, phone number, hashed password, account settings, authentication dataReset the password at next login; change it anywhere it was reused
API customerAPI keys and OAuth tokensGenerate a new API key and delete the old one
Authenticator-app MFA userMulti-factor authentication dataDelete and reset the authenticator entry
Signer without an accountEmail address and nameNo reset; watch for phishing that uses the name
Account made with "Sign up with Google"No password storedNone for the password

The last row comes from the notice: accounts created without a Dropbox Sign password had no password stored or exposed. The phishing advice in the fourth row is ours, not Dropbox's.

Is a linked Dropbox account affected?

Dropbox says no. Based on its investigation, it believes the incident stayed within Dropbox Sign infrastructure and did not affect other Dropbox products. It still advised anyone who reused a Dropbox Sign password elsewhere to change it and turn on multi-factor authentication.

Did Dropbox's finances take a hit?

The company says the incident has not had a material effect on its business operations and that it does not expect one. On finances, it says it had not yet determined whether the incident was reasonably likely to have a material impact. It names remaining risks and says remediation continues.

What do Dropbox's later reports say?

Dropbox's next filings settle the question its 8-K left open on finances. The 10-Q filed on August 9, 2024 says the incident has not had, and Dropbox does not believe it is likely to have, a material impact on its overall financial condition or results of operations. The annual report for 2024, filed on February 21, 2025, repeats that position and adds that no facts had come to light pointing the other way. Both reports date the discovery to April 2024 and point back to the May 1, 2024 8-K.

What is still unknown?

The investigation was still running when the filing was made. The filing does not state how the actor first gained access, how long the access lasted, or the number of Dropbox Sign users. Dropbox's notice said it expected to finish notifying affected users within a week. No amended 8-K is on record here.

How this disclosure's timing compares

Dropbox disclosed 7 days after the discovery date its filing gives. Across the 46 other filings under 8-K Item 1.05 on cisonews.net that date discovery to the day, the median gap is 6 days.

The rule behind an Item 1.05 filing

Form 8-K Item 1.05 is where a public company reports a cybersecurity incident it has determined to be material. Under the rule the SEC adopted on July 26, 2023, the filing is generally due four business days after the company determines that the incident is material. Source: U.S. Securities and Exchange Commission, press release 2023-139. The guide What is SEC Form 8-K Item 1.05, and what counts as a disclosed cyber incident? reads the rule in full, and the glossary defines Form 8-K Item 1.05.

Other technology incidents on cisonews.net

  • DreamHost, Breach notice, first disclosed November 2, 2026
  • Photon Health, Breach notice, first disclosed October 28, 2026; affected: approximately 1706 Rhode Island residents
  • Indico Data Solutions, Breach notice, first disclosed October 27, 2026; affected: 79 Rhode Island residents
  • Stitch Connect Inc, Breach notice, first disclosed September 21, 2026; affected: 113,727 people in total (Indiana AG record)
  • IDScan.net, Breach notice, first disclosed September 18, 2026; 27,624 affected in total (Indiana Attorney General)

All technology incidents

Sources

  1. 2024-05-01 · ADropbox, Inc., Form 8-K (SEC EDGAR), published May 1, 2024
  2. 2024-08-09 · ADropbox, Inc., Form 10-Q for the quarter ended June 30, 2024, published August 9, 2024
  3. 2025-02-21 · ADropbox, Inc., Form 10-K for the year ended December 31, 2024, published February 21, 2025
  4. 2024-05-01 · ADropbox, Inc., Exhibit 99.1 to Form 8-K: A Recent Security Incident Involving Dropbox Sign (SEC EDGAR), published May 1, 2024
  5. 2023-07-26 · AU.S. Securities and Exchange Commission, press release 2023-139, published July 26, 2023

Tier A: the organization itself (including notices it filed with a state attorney general), a regulator or SEC EDGAR. Tier B: established press. Each fact on this page carries its supporting passage in the page source.

Entries like this one, in Wednesday’s docket

Wednesdays

Unsubscribe any time.