\n<\/p>\n
Six months ago, Mercor was flying high after raising a massive $350 million Series C<\/a> that valued the AI data training startup at $10 billion. But after admitting on March 31 that it was the target of a data breach<\/a>, the company has been facing a world of trouble.<\/p>\n Since then, a hacker group has claimed to have obtained 4TB of stolen data from Mercor\u2019s systems, including candidate profiles, personally identifiable information, employer data, source code, and API keys. Mercor has not commented on the authenticity of the data, reiterating only that it is investigating and \u201cwill continue to communicate with our customers and contractors directly as appropriate and devote the resources necessary to resolving the matter as soon as possible.\u201d<\/p>\n Mercor said its data breach was the result of a hack of the open source tool LiteLLM<\/a>. This tool is so popular that it\u2019s downloaded millions of times a day. For 40 minutes, the tool harbored credential harvesting malware \u2014 rogue software that could steal login credentials. Those credentials were used to gain access to more software and accounts, which it used to harvest more credentials, and so on.<\/p>\n While there have been no formal acknowledgments of how much data was scooped up from Mercor, there have been repercussions all the same. Meta has paused its contracts with Mercor indefinitely, sources told Wired<\/a>. (Mercor declined to comment to TechCrunch about this.)<\/p>\n Like other contract AI data training companies, Mercor handles some of the model makers\u2019 biggest trade secrets: the custom data sets and processes they use to teach their models. This is so important to them that even after Meta spent $14.3 billion on Mercor\u2019s competitor Scale AI<\/a>, it continued working with Mercor.<\/p>\n In a spot of good news for Mercor (maybe\u2026we\u2019ll see): OpenAI also confirmed to Wired that it was investigating its exposure in Mercor\u2019s breach, but said it had not paused or ended its contracts at the time. However, TechCrunch has heard from multiple sources that other large model makers may also be weighing their relationships with Mercor after the breach, although we have not confirmed enough details to name names as of yet. <\/p>\n In the meantime, five of Mercor\u2019s contractors have filed lawsuits, Business Insider reports<\/a>, over their alleged personal data exposure. Whether these suits represent a serious threat or are just opportunistic and a nuisance remains to be seen. (Mercor declined to comment.)<\/p>\n Techcrunch event<\/p>\n \n\t\t\t\t\t\t\t\t\tSan Francisco, CA<\/span> One lawsuit, reviewed by TechCrunch, even named LiteLLM and Delve as defendants. This is wild, and perhaps a stretch, but here\u2019s the connection: LiteLLM used AI compliance startup Delve to obtain its security certifications. Delve has been accused <\/a>by an anonymous whistleblower of allegedly faking data for security certifications and using rubber-stamping auditors.<\/p>\n A security certification does not directly prevent hackers from launching successful attacks, but it is intended to ensure that companies have processes in place to minimize such threats.<\/p>\n Although Delve has denied those allegations while simultaneously instituting operational changes, it has been in a world of hurt of its own, to the point where Y Combinator severed ties<\/a> with the company.<\/p>\n LiteLLM ditched Delve<\/a> and is now working with another AI compliance startup to obtain its security certifications again. LiteLLM also published a complete report<\/a> on the security incident.<\/p>\n But Mercor itself was not a Delve customer, the company confirmed to TechCrunch. If, however, the fallout for Mercor continues, a lot of revenue could be at stake. The company was reportedly on pace to hit over $1 billion in annualized revenue earlier this year before the data leak, an anonymous source told The Information.<\/a><\/p>\n<\/div>\n
\n\t\t\t\t\t\t\t\t\t\t\t\t\t|<\/span>
\n\t\t\t\t\t\t\t\t\t\t\t\t\tOctober 13-15, 2026<\/span>\n\t\t\t\t\t\t\t<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/div>\n