LexisNexis has taken three Nexis products, Diligence, Metabase API, and Newsdesk, offline after detecting unusual activity on a third-party vendor’s servers. No data exposure has been confirmed, and the company says it isn’t connected to last week’s separate Metabase Cloud SQL injection zero-day that hit Framework and Tally.
More details here: LexisNexis shuts down services after suspicious activity on servers
The company said it is investigating the incident with assistance from a cybersecurity forensic firm and is rebuilding affected systems in a new environment before bringing the services back online.
“Earlier this week, we identified unusual activity on servers that are hosted and managed by a third-party vendor,” reads the notification sent to customers last week.
“To protect our customers and contain the issue at its source, we made the immediate decision to disconnect from those third-party systems.”
Amit Shuster, VP Product & Engineering, Vetric had this to say:
“An outage like this doesn’t announce itself as a security story. It shows up as teams that suddenly can’t see what they could see yesterday, even though nothing in their own environment changed. For investigators and trust and safety teams working time-sensitive cases, lost visibility means a stalled case, and threats don’t pause while service is restored. That’s why the organizations on the front lines are getting deliberate about resilience, working with partners alongside their existing sources, so one provider’s bad week never becomes their blind spot.”
This is a security story. And I hope that LexisNexis is honest about this so that we can all learn from it not to mention find out what happened and how it was addressed. Not to mention that the vendors that you work with are your weakest point and every organization needs to address this ASAP.
Related
This entry was posted on August 11, 2026 at 11:49 am and is filed under Commentary with tags LexisNexis. You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
LexisNexis pulls data services offline after unusual activity on a third-party vendor’s servers
LexisNexis has taken three Nexis products, Diligence, Metabase API, and Newsdesk, offline after detecting unusual activity on a third-party vendor’s servers. No data exposure has been confirmed, and the company says it isn’t connected to last week’s separate Metabase Cloud SQL injection zero-day that hit Framework and Tally.
More details here: LexisNexis shuts down services after suspicious activity on servers
The company said it is investigating the incident with assistance from a cybersecurity forensic firm and is rebuilding affected systems in a new environment before bringing the services back online.
“Earlier this week, we identified unusual activity on servers that are hosted and managed by a third-party vendor,” reads the notification sent to customers last week.
“To protect our customers and contain the issue at its source, we made the immediate decision to disconnect from those third-party systems.”
Amit Shuster, VP Product & Engineering, Vetric had this to say:
“An outage like this doesn’t announce itself as a security story. It shows up as teams that suddenly can’t see what they could see yesterday, even though nothing in their own environment changed. For investigators and trust and safety teams working time-sensitive cases, lost visibility means a stalled case, and threats don’t pause while service is restored. That’s why the organizations on the front lines are getting deliberate about resilience, working with partners alongside their existing sources, so one provider’s bad week never becomes their blind spot.”
This is a security story. And I hope that LexisNexis is honest about this so that we can all learn from it not to mention find out what happened and how it was addressed. Not to mention that the vendors that you work with are your weakest point and every organization needs to address this ASAP.
Share this:
Like this:
Related
This entry was posted on August 11, 2026 at 11:49 am and is filed under Commentary with tags LexisNexis. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.