LexisNexis Breach Incident Score: Analysis & Impact (LEX1772584112)

In this Rankiteo incident briefing, we review the LexisNexis breach identified under incident ID LEX1772584112.

The analysis begins with a detailed overview of LexisNexis's information like the linkedin page: https://www.linkedin.com/company/lexisnexis, the number of followers: 391074, the industry type: IT Services and IT Consulting and the number of employees: 10705 employees

After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 760 and after the incident was 705 with a difference of -55 which is could be a good indicator of the severity and impact of the incident.

In the next step of the video, we will analyze in more details the incident and the impact it had on LexisNexis and their customers.

On 30 July 2025, LexisNexis disclosed Data Breach issues under the banner "LexisNexis Data Breach Affecting Legacy Customer Data".

LexisNexis, the legal and business intelligence provider, confirmed a data breach involving legacy servers containing customer information.

The disruption is felt across the environment, affecting Legacy servers (deprecated data from before 2020), and exposing Names, business contact details, user identities, product usage records, IP addresses, support ticket data.

In response, moved swiftly to contain the threat with measures like Breach contained following investigation, and stakeholders are being briefed through Notified affected current and former customers.

The case underscores how Contained, with advisories going out to stakeholders covering Notified affected current and former customers.

Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.

The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.

Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Exploit Public-Facing Application (T1190) with high confidence (90%), supported by evidence indicating unpatched React2Shell vulnerability in a frontend application. Under the Execution tactic, the analysis identified Exploitation for Client Execution (T1203) with moderate to high confidence (80%), supported by evidence indicating react2Shell vulnerability exploited in frontend application. Under the Persistence tactic, the analysis identified Valid Accounts (T1078) with moderate to high confidence (70%), supported by evidence indicating access to AWS infrastructure via compromised credentials implied. Under the Privilege Escalation tactic, the analysis identified Exploitation for Privilege Escalation (T1068) with moderate to high confidence (70%), supported by evidence indicating react2Shell vulnerability may have enabled privilege escalation. Under the Defense Evasion tactic, the analysis identified Valid Accounts (T1078) with moderate to high confidence (70%), supported by evidence indicating legacy servers accessed; no evidence of compromise to active products and Impair Defenses: Disable or Modify Tools (T1562.001) with moderate confidence (50%), supported by evidence indicating unpatched vulnerability suggests lack of monitoring/updates. Under the Credential Access tactic, the analysis identified Steal Application Access Token (T1528) with moderate confidence (60%), supported by evidence indicating aWS infrastructure accessed; tokens may have been compromised. Under the Discovery tactic, the analysis identified Account Discovery (T1087) with moderate to high confidence (70%), supported by evidence indicating user identities and product usage records accessed and Network Service Discovery (T1046) with moderate confidence (60%), supported by evidence indicating legacy servers containing deprecated data targeted. Under the Collection tactic, the analysis identified Data from Local System (T1005) with high confidence (90%), supported by evidence indicating names, business contact details, IP addresses, support ticket data and Data from Information Repositories (T1213) with moderate to high confidence (80%), supported by evidence indicating legacy servers with customer data accessed. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), supported by evidence indicating 2GB of files posted in underground forums by FulcrumSec. Under the Impact tactic, the analysis identified Data Destruction (T1485) with lower confidence (30%), supported by evidence indicating no evidence of data destruction; legacy data only and Data Manipulation: Stored Data Manipulation (T1565.001) with lower confidence (40%), supported by evidence indicating legacy data accessed; potential for manipulation. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.