People search D&B data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 2 D&B-linked incidents, with headline counts up to 1M+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why D&B breach history matters
D&B operates in Technology. 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
2014 — — D&B: Hackers stole millions of social security numbers…
Cataloged incident. Hackers stole millions of social security numbers from large US data brokers Dun & Bradstreet Corp and Kroll Background America Inc, owned by Altegrity. Correction 7 Jan 2015: we previously stated that records were stolen from LexisNexis. LexisNexis conducted a thorough investigation of the malware intrusion and found no evidence that the malware accessed or stole any customer or consumer data. BreachHistory cites approximately 1M+ affected records in this row. See the d-bu and canonical BreachHistory entry.
2013 — — D&B: Hackers stole millions of social security numbers…
Cataloged incident. Sep 2013. Hackers stole millions of social security numbers from large US data brokers Dun & Bradstreet Corp and Kroll Background America Inc, owned by Altegrity. Correction 7 Jan 2015: we previously stated that records were stolen from LexisNexis. LexisNexis conducted a thorough investigation of the malware intrusion and found no evidence that the malware accessed or stole any customer or consumer data. BreachHistory cites approximately 1M+ affected records in this row. See the d-b2013 and canonical BreachHistory entry.
Patterns and analysis
- Mixed intrusion and disclosure events — appears across multiple D&B 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 D&B company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/d-b · Latest: d-bu.
Sources: BreachHistory catalog (2 rows for D&B), company and regulator disclosures cited in individual breach records.