LexisNexis Data Breach History

This page tracks the LexisNexis data breach history and cybersecurity incidents affecting LexisNexis (United States). BreachHistory currently indexes 10 publicly disclosed or catalogued incidents spanning 2005 through 2026, with approximately 5.6 million records reported as exposed across all indexed events. These totals may include overlapping datasets or third-party estimates and should not be interpreted as unique affected users.

The LexisNexis breach timeline includes major data breaches, cyber attacks, data leaks, credential exposures, API abuse, and other security incidents. Each incident provides details on the estimated records exposed, attack method, affected data types, and supporting public sources. Currently, 0 incidents are company-confirmed, while 1 remain unverified claims pending independent verification.

Largest LexisNexis Data Breaches

The largest indexed incidents include the 2026 LexisNexis Legal & Professional — 3.9M records (FulcrumSec, React2Shell / Rea…, the 2014 — LexisNexis: Hackers stole millions of social security numbers -…, and the 2026 LexisNexis Risk Solutions — FulcrumSec AWS breach (~364K profiles; React2Shel…, along with additional historical incidents involving exposed passwords, public databases, and large-scale data scraping. Record counts originating from threat actors or leak sites should be treated as estimates unless confirmed by LexisNexis or a regulator. Below is the list of large data breaches:

• 2026 2026 LexisNexis Legal & Professional — 3.9M records (FulcrumSec, React2Shell / Reach2Shell) — about 3.9M records exposed · Catalogued incident
• 2014 2014 — LexisNexis: Hackers stole millions of social security numbers -… — about 1.0M records exposed · Catalogued incident
• 2026 2026 LexisNexis Risk Solutions — FulcrumSec AWS breach (~364K profiles; React2Shell / Reach2Shell) — about 364.3K records exposed · Catalogued incident
• 2005 2005 — LexisNexis: Unauthorized individuals used IDs and passwords of… — about 310.0K records exposed · Catalogued incident
• 2009 2009 — LexisNexis: Companies Lexis Nexis and Investigative… — about 40.0K records exposed · Catalogued incident
• 2013 2013 — LexisNexis: LexisNexis informed Sprechman & Associates that the… — about 20.0K records exposed · Unverified claim
• 2006 2006 — LexisNexis: A package containing an employee's laptop computer… — about 449 records exposed · Catalogued incident
• 2007 2007 — LexisNexis: LexisNexis sent out notification letters of two… — about 220 records exposed · Catalogued incident

What Information Was Exposed?

Depending on the incident, exposed data may include names, and other personal information (PII). The exact data varies between incidents, so review each breach page before assuming your information was affected.

LexisNexis Data Breach 2026

At the time of this update, BreachHistory catalogues 3 2026 incidents related to LexisNexis. Most recent entry: 2026 LexisNexis Risk Solutions — FulcrumSec AWS breach (~364K profiles; React2Shell / Reach2Shell). New incidents are added as official disclosures, regulatory filings, or credible cybersecurity reports become available.

What To Do If You Were Affected

If you believe your account may have been involved in a LexisNexis data breach, change any reused passwords, enable multi-factor authentication (MFA), monitor your account for suspicious activity, and be cautious of phishing emails or fake breach notifications.

This LexisNexis breach history is maintained by BreachHistory using public disclosures, regulatory filings, security research, and clearly labelled third-party claims. For the complete breach timeline, records exposed, incident details, and AI Breach Risk Score, explore the sections on this page.