Mercor Confirms Cyberattack Tied to Open-Source LiteLLM Supply Chain Compromise

What happened

Mercor confirmed a cyberattack tied to the compromise of the open-source LiteLLM project after saying it was one of thousands of companies affected by the recent incident. The security issue was linked to the LiteLLM compromise, which the article says was tied to the hacking group TeamPCP. The report also said extortion group Lapsus$ claimed it had targeted Mercor and gained access to company data. Mercor spokesperson Heidi Hagberg said the company moved promptly to contain and remediate the incident and is conducting a thorough investigation with third-party forensics experts. A sample of allegedly stolen data it reviewed included material referencing Slack data, apparent ticketing data, and two videos purportedly showing conversations between Mercor’s AI systems and contractors on its platform. 

Who is affected

The direct exposure affects Mercor and potentially its customers and contractors, though the company declined to say whether any customer or contractor data had been accessed, exfiltrated, or misused. The article also says it remains unclear how many companies were affected by the LiteLLM-related incident overall. 

Why CISOs should care

This matters because the incident links a supply chain compromise in an open-source dependency to follow-on claims of data theft at a fast-growing AI company. It also shows how a single compromised project can create uncertainty not just about internal system access, but about whether customer or contractor data was exposed, while investigations are still underway. 

3 practical actions

1. Treat open-source dependencies as incident entry points: Review whether widely used open-source components in development and production workflows could create downstream exposure if a package compromise affects credentials or build environments. 
2. Scope contractor and collaboration-system exposure early: Prioritize verification of whether collaboration platforms, ticketing systems, or contractor-facing environments were accessed, since the sample described in the report referenced Slack data, ticketing data, and contractor interactions. 
3. Plan for parallel claim verification and forensic response: Be ready to investigate both the initial supply chain compromise and any later extortion or leak claims, since Lapsus$ separately claimed it had targeted Mercor. 

For more news about intrusions tied to compromised software dependencies and stolen internal data, click Cyberattack to read more.