Mercor Confirms Data Breach Via LiteLLM Supply Chain Attack — A Warning Shot for AI Infrastructure Security
AI recruiting startup Mercor has confirmed a cyberattack tied to a compromise of the widely-used open-source LiteLLM gateway project, with a Lapsus$-affiliated extortion crew claiming responsibility — exposing a critical security gap in the AI startup ecosystem's reliance on shared open-source infrastructure.

D.O.T.S AI Newsroom
AI News Desk
Mercor, an AI-powered recruiting startup that automates talent sourcing and candidate evaluation for technology companies, has confirmed it was the victim of a cyberattack executed through a compromised dependency in its technology stack. The attack vector: LiteLLM, one of the most widely deployed open-source AI gateway libraries in the startup ecosystem, which had been compromised by a malicious actor prior to Mercor's breach.
What LiteLLM Is and Why This Matters
LiteLLM is not a household name outside of AI engineering circles, but it is infrastructure. The open-source library functions as a universal gateway that allows developers to call any major AI model — GPT, Claude, Gemini, Llama — through a single standardized API. It is, in effect, the plumbing that sits between an AI application and the AI models it uses. The project has tens of thousands of GitHub stars and is installed in a significant fraction of AI applications built by startups and enterprises in 2025 and 2026.
When LiteLLM itself was compromised — through what appears to have been a credential-stealing malware attack that exploited LiteLLM's relationship with a security compliance vendor called Delve — any company using LiteLLM became a potential attack surface. Mercor was among the victims.
The Lapsus$ Connection
The threat actor claiming responsibility for the Mercor breach is affiliated with Lapsus$, the extortion hacking group that made headlines between 2021 and 2023 for breaching Microsoft, Nvidia, Samsung, Okta, and Rockstar Games. Lapsus$ operates through social engineering, credential theft, and supply chain compromises rather than zero-day exploits — a methodology that has proven devastatingly effective against technology companies that trust their software dependencies.
The group's return to prominence via AI infrastructure targeting is significant. Earlier Lapsus$ operations focused on credential theft from identity providers and source code repositories. Targeting an AI gateway library suggests the group has adapted its playbook to the current technology landscape — where AI infrastructure components are widely shared, rapidly deployed, and often inadequately secured.
The Supply Chain Vulnerability Pattern
The Mercor breach follows a now-familiar pattern that security researchers have been warning about for years: an attack that compromises not the target directly, but a trusted component in the target's supply chain. The SolarWinds breach of 2020 established the template. The Log4Shell vulnerability demonstrated how deep open-source dependencies can run. The LiteLLM compromise is the AI-era version of the same structural problem.
What makes AI infrastructure supply chains particularly vulnerable is their newness. The LiteLLM ecosystem, like much of the AI tooling stack, was built at startup speed in 2023 and 2024 — prioritizing capability and developer experience over security architecture. Security compliance processes, penetration testing protocols, and dependency auditing practices that are standard in enterprise software simply have not had time to mature in the AI tooling layer.
What Mercor Has Disclosed
Mercor confirmed the breach but has not disclosed the specific data accessed by the attackers, the number of individuals whose information may have been compromised, or the timeline of the intrusion. Given that Mercor's product involves sensitive hiring data — resumes, technical assessments, compensation data, and company-side hiring criteria — the potential scope of the breach is material for both the company and its enterprise clients.
The extortion component of the attack — where the hacking crew publicly claimed responsibility — is a pressure tactic designed to accelerate ransomware payments or data deletion agreements. Whether Mercor paid a ransom has not been disclosed.
The Industry Implication
Every AI startup that relies on LiteLLM should be conducting an immediate audit of their dependency versions, reviewing access logs for anomalous behavior during the period of the LiteLLM compromise, and assessing whether their API keys or customer data were exposed. The AI infrastructure supply chain is, as of today, a documented attack surface for sophisticated threat actors.