People search DocuSign data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 2 DocuSign-linked incidents. This page maps every attested event through 2026 with internal links to canonical records.
Why DocuSign breach history matters
DocuSign operates in Technology (United States). Across indexed rows, recurring themes include mixed intrusion and disclosure events. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2017 — — DocuSign: DocuSign, a major provider of electronic signature…
Cataloged incident. DocuSign, a major provider of electronic signature technology, acknowledged today that a series of recent malware phishing attacks targeting its customers and users was the result of a data breach at one of its computer systems. The company stresses that the data stolen was limited to customer and user email addresses, but the incident is especially dangerous because it allows attackers to target users who may already be expecting to click on links in emails from DocuSign.San Francisco-based Doc Exposed categories include Personal information. No attested victim count is published for this row yet. See the docusign2017 and canonical BreachHistory entry.
2012 — — DocuSign: DocuSign user information was discovered to be…
Unverified claim — treat actor counts cautiously. DocuSign user information was discovered to be accessible through a Google search. The information goes as far back as January 2012, and some information could be even older. It is possible to see private emails, signatures, times, dates, locations, addresses, document names, and email addresses. DocuSign claims that the information is available because a small number of DocuSign users have saved their own personal copies of their signed documents to publicly accessible and searchable location Exposed categories include Personal information. No attested victim count is published for this row yet. See the docusign2012 and canonical BreachHistory entry.
Patterns and analysis
- Mixed intrusion and disclosure events — appears across multiple DocuSign 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 DocuSign company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/docusign · Latest: docusign2017.
Sources: BreachHistory catalog (2 rows for DocuSign), company and regulator disclosures cited in individual breach records.