CYBERSECURITYTRACKER
TRACKING7,631 stories in this site build1,635 vulnerability news stories in this site build
Permanent story citation

LexisNexis shuts down services after suspicious activity on servers

This page keeps the story as Cybersecurity Tracker first published it. If the tracker later corrects it, the correction appears below the original and never replaces it.

Back to newsStory 4129

As cited

Copy frozen at (site build).

breaches incidents

LexisNexis shuts down services after suspicious activity on servers

LexisNexis disabled access to its Diligence, Metabase API, and Newsdesk services after discovering suspicious activity on servers operated by a third-party vendor. The company initiated an investigation into the incident but did not disclose the scope of any potential data exposure or the timeline for service restoration.

Why it matters: LexisNexis customers and users of these services face operational disruption; practitioners should monitor for incident updates and assess whether data was accessed or exfiltrated, as LexisNexis processes sensitive business intelligence and legal information.

Source published
First seen by Cybersecurity Tracker

Source attribution

Correction

Correction recorded as of .

breaches incidents

LexisNexis shuts down services after suspicious activity on servers

No summary had been written when this copy was frozen.

First seen by Cybersecurity Tracker

Source attribution

Correction

Correction recorded as of .

breaches incidents

LexisNexis shuts down services after suspicious activity on servers

LexisNexis temporarily disabled its Diligence, Metabase application programming interface, and Newsdesk services after detecting unusual activity on servers managed by a third-party vendor. The company has not identified the vendor or detailed the nature of the suspicious behavior. Services remain offline as part of the response effort.

Why it matters: Customers of LexisNexis Diligence, Metabase API, or Newsdesk face service disruption and should assess contingency plans for affected workflows.

Source published
First seen by Cybersecurity Tracker

Source attribution

Glossary