Mercor's 2026 security incident, and the lessons for anyone licensing records

Nobody broke into Mercor directly. Someone slipped malicious code into LiteLLM releases, and every system that installed those releases leaked its credentials. Mercor happened to run the bad versions, which is what security teams call a supply chain attack.

The main group at risk was Mercor's contractor network: physicians, attorneys, engineers and other specialists paid to train AI models. The company keeps close to five million of these profiles and says sensitive details leaked for only a small slice of them.

According to Mercor, staff records were untouched and customer exposure was minimal, partly because clients such as Anthropic, OpenAI and Meta keep much of the work inside their own systems. No total has been published by Mercor or by any independent source.

Mercor's June statement lists the following: every outside library it uses now gets reviewed, credentials and keys have been replaced, cloud and network rules are stricter, independent testers probe its defences, and monitoring runs 24 hours a day. It also points to a SOC 2 Type II report and says labs never receive a seller's raw files.

All reasonable. The incident still shows what an audit certificate cannot promise: Mercor had one, and the weak point was software it had every reason to trust.

Each extra copy of your records is one more place it can escape from, whoever holds it. The answer is a sharper list of questions for every buyer, broker or marketplace you speak to.

• Retention and deletion. How many days do you hold our copy, and how is it wiped? micro1's public terms set 120 days after final delivery. Put a figure in your own contract.
• System access. Will you log into our tools? A law firm that advises sellers suggests refusing direct access and handing over an export you or your own contractor have cleaned.
• Breach notice. How many days after you discover a breach will you tell us?
• Liability. What is the cap, and which side indemnifies the other?

Treat the incident as a prompt to press every buyer harder on security, Mercor among them. By itself it does not disqualify Mercor. Compare what each buyer will sign up to on retention, access and notice, then decide.

Our Mercor review scores it on exactly these points, and micro1 vs Mercor puts the two side by side.