As of November 16, 2026 the case is stayed pending mediation (order of July 21, 2026), with no ruling on the merits, no class certified and no settlement on the record.
Seven complaints filed from April 1, 2026 were merged on May 19, 2026, so counts of "four" or "five" lawsuits describe the period before consolidation.
The case belongs to the independent reference on AI training data licensing because it concerns the people who produce human data for AI labs. DataPacts is not affiliated with any party and gives no legal advice.
Dates, dockets and quotations on this page come from the court filings and the California Attorney General notice named in each table, read on November 16, 2026, and how figures are sourced and dated is set out on the methodology page.
The Mercor Breach Case at a Glance: Court, Lead Docket, Parties and Status
No court has ruled on the merits: the case was consolidated on May 19, 2026, a consolidated complaint followed on June 18, 2026, and all proceedings have been stayed for mediation since July 21, 2026. The table gives the case facts as of 2026-11-16.
| Field | Value | Source |
|---|---|---|
| Case | In re Mercor.io Corporation Data Breach Litigation | Dkt. 29; Dkt. 44 |
| Court | U.S. District Court, N.D. Cal., San Francisco | Dkt. 29; Dkt. 31 |
| Docket | Lead Case No. 3:26-cv-02821-WHO (the first-filed Deboni action) | Dkt. 29; Dkt. 44 |
| Judge | William H. Orrick | Dkt. 29; Dkt. 44 |
| First complaint | 2026-04-01 (Deboni v. Mercor.io Corporation) | Dkt. 1 |
| Consolidated | 2026-05-19: seven actions, Fed. R. Civ. P. 42(a) | Dkt. 29 |
| Defendant | Mercor.io Corporation | Dkt. 31 |
| Plaintiffs | putative classes of applicants, employees and contractors | Dkt. 31 |
| Operative complaint | consolidated class action complaint, 2026-06-18, six counts, jury demand | Dkt. 31 |
| Status | stayed pending mediation since 2026-07-21; no response to the complaint, no class certified, no settlement | Dkt. 44; CourtListener docket feed |
| Breach dates reported | 2026-03-24 and 2026-03-30 | California AG report sb24-625431 |
How Seven Breach Complaints Became One Consolidated Case
Judge William H. Orrick consolidated seven putative class actions against Mercor.io Corporation into the first-filed Deboni action on May 19, 2026, for all purposes including pretrial proceedings and trial under Federal Rule of Civil Procedure 42(a) (Dkt. 29).
Deboni v. Mercor.io Corporation was filed on April 1, 2026 (Dkt. 1). The Deboni plaintiff moved to consolidate (Dkt. 17), a related-case order followed on April 24, 2026 (Dkt. 22), and Mercor did not oppose consolidation (Dkt. 29).
The order directs the clerk to administratively close the other actions, files everything under the lead number with the caption "In re Mercor.io Corporation Data Breach Litigation", deems earlier filings part of the record, and sends any later class action on the same alleged facts into the same case.
Mercor answers only the consolidated complaint. The court also appointed John J. Nelson of Milberg PLLC as interim lead counsel for all plaintiffs in the same order, which calls the appointment interim and open to change at any time (Dkt. 29).
The March 2026 Breach Behind the Suits, as Mercor Reported It
Mercor.io Corporation reported to the California Attorney General that unauthorized access occurred on March 24 and March 30, 2026, and its consumer notice dated June 25, 2026 says malware inserted into certain versions of LiteLLM, in the notice's words "its widely used code scanning tool", let an unauthorized actor access some of its systems between March 24 and 30. The notice says the actor downloaded data, offers 24 months of TransUnion credit monitoring with enrollment by October 1, 2026 (a date that has passed), and states "In early April, we emailed you about a security incident".
Mercor's breach record, its own "very limited subset" statement and what both mean for its programs are set out in Mercor's profile as a data buyer, with its breach record.
What the Consolidated Complaint Claims: Six Counts Against Mercor.io
The consolidated class action complaint of June 18, 2026 pleads six counts: three for a nationwide class (negligence, breach of implied contract, unjust enrichment) and three under California law for a California subclass (constitutional privacy, the California Consumer Privacy Act and the Unfair Competition Law). The table lists each count with its status as of 2026-11-16.
| Count | Claim | Law | For whom | Status 2026-11-16 | Source |
|---|---|---|---|---|---|
| One | negligence | common law | plaintiffs and nationwide class | pending, stayed | Dkt. 31; Dkt. 44 |
| Two | breach of implied contract | common law | nationwide class | pending, stayed | Dkt. 31; Dkt. 44 |
| Three | unjust enrichment | common law | nationwide class | pending, stayed | Dkt. 31; Dkt. 44 |
| Four | invasion of privacy | California Constitution, art. I, sec. 1 | California subclass | pending, stayed | Dkt. 31; Dkt. 44 |
| Five | California Consumer Privacy Act | Cal. Civ. Code 1798.100 et seq. (1798.150) | California subclass | pending, stayed | Dkt. 31; Dkt. 44 |
| Six | unfair competition | Cal. Bus. & Prof. Code 17200 et seq. | California subclass | pending, stayed | Dkt. 31; Dkt. 44 |
Every statement in the complaint is an allegation, and the plaintiffs demand a jury trial. The CCPA count rests on Cal. Civ. Code 1798.150, the private right of action for data breaches, and CCPA and California law on training data explains what the statute covers beyond breaches. No count has been decided.
Who the Proposed Nationwide Class and California Subclass Cover
The proposed nationwide class covers all United States residents whose private information was actually or potentially accessed during the Mercor breach, including everyone who received a notice of it. The California subclass is the same group limited to California residents and is represented by one named plaintiff.
The proposed definitions exclude Mercor and its affiliates, judges, government entities and timely opt-outs, and the plaintiffs reserve the right to change them. The complaint describes the people as Mercor's "current and former applicants, employees, and contractors". No class has been certified.
What Data the Plaintiffs Say Was Exposed
The plaintiffs allege that Mercor collected Social Security numbers, W-9 tax details, passport and other ID scans, interview recordings, screenshots, resumes and onboarding documents from candidates, and that names, Social Security numbers, video interview recordings and identity documents were compromised.
The complaint quotes Mercor's own tax pages on why Social Security numbers are collected (Form 1099-NEC) and alleges that candidate profiles hold work product and interview footage that could be used to imitate people.
The complaint's figures for stolen volume and affected people rest on press reports and are not repeated here. Mercor states that a very limited subset of its experts had sensitive information affected (Mercor blog, checked 2026-11-16).
On notice, the complaint alleges that Mercor began emailing on or about March 31, 2026 with "almost nothing" of relevant content, while Mercor's notice says it emailed in early April. Both versions stay as written, and neither is decided.
What the Plaintiffs Ask the Court to Order
The plaintiffs ask for class certification, damages, restitution and fees, and an injunction requiring Mercor to change its security practices. The complaint names no amount in a figure. The requested relief is:
- class certification and appointment of class counsel;
- actual and statutory damages, restitution, fees and costs;
- injunctive relief including third-party security audits and penetration tests, automated monitoring and staff training;
- segmentation of stored data.
Mercor Breach Case Docket Entries, April to November 2026
Nine rows carry the case from the first complaint to the latest filing on the docket. The table lists them as of 2026-11-16, and no later entry was on the public docket that day.
| Date | Entry | What it decided or reported | Source |
|---|---|---|---|
| 2026-04-01 | Dkt. 1 | Deboni class action complaint with jury demand | Court PDF (archive.org) |
| 2026-04-24 | Dkt. 22 | Related-case order: later Mercor breach actions related to Deboni before Judge Orrick | CourtListener docket feed |
| 2026-05-19 | Dkt. 29 | Order granting consolidation of seven actions and appointing interim lead counsel; others administratively closed | Court PDF (archive.org) |
| 2026-06-18 | Dkt. 31 | Consolidated class action complaint, six counts | Court PDF (archive.org) |
| 2026-07-14 and 2026-07-15 | Dkt. 34 to 42 | ADR certifications by the parties | CourtListener docket feed |
| 2026-07-20 | Dkt. 43 | Stipulation to stay proceedings pending mediation | CourtListener docket feed |
| 2026-07-21 | Dkt. 44 | Order granting the stay; case management conference and deadlines vacated | Court PDF (archive.org) |
| 2026-08-03 and 2026-08-04 | per Dkt. 44 | Response deadline and initial conference, both stayed or vacated | Court PDF (archive.org) |
| 2026-11-05 | Dkt. 45 | Notice of change of address | CourtListener docket feed |
The Stay Pending Mediation and What the Docket Shows Next
On July 21, 2026 Judge Orrick granted the parties' stipulation to stay all proceedings pending a confidential mediation, vacating the case management conference of August 4, 2026 and staying Mercor's deadline to respond to the consolidated complaint (Dkt. 44).
The stipulation of July 20, 2026 (Dkt. 43) names a retired judge as mediator and was the parties' first request to change time since consolidation.
The parties must file a joint status report no later than 14 days after mediation ends, saying whether the stay should continue. Mercor has filed no answer and no motion to dismiss.
As of November 16, 2026 the last entry is a notice of change of address dated November 5, 2026 (Dkt. 45). No status report, settlement, motion for preliminary approval or claim process appears, so the case is stayed, not settled.
The case also sits in the register of dated breaches and complaints against data buyers, next to the other incidents of companies that collect data for AI.
What the Case Means for Contributors and for Companies Connecting Data to Mercor
For contributors, the case is a pending claim with no settlement and no class certified, so nothing on the record yet decides who is a class member or what anyone receives.
The notice and its enrollment date are the dated record each person holds, and what platforms collect from contributors and what a breach notice means are covered under contributor privacy on human data platforms.
For companies, Mercor's company data program page states SOC 2 Type II and that "No AI lab buyer or third-party vendor ever sees your raw data" (Mercor's claims, checked 2026-11-09).
The complaint alleges that source code, keys and secrets and VPN data were also accessed, citing press reports, and no record read states that company data licensed to Mercor was affected. How a seller weighs a buyer's record is covered under security and breach risk during an AI data sale.
Where the Mercor Breach Case Sits Among Contributor and Privacy Proceedings
The Mercor breach case is one of the related proceedings the case tracker follows next to the training-data lawsuits, because it concerns the people who produce human data rather than the data used for training.
The case tracker of AI lawsuits over training data lists every tracked case and related proceeding, and the table compares four of them as of 2026-11-16.
| Proceeding | Forum and docket | Status | Page |
|---|---|---|---|
| McKinney v. Scale AI | San Francisco Superior Court CGC-24-620481 | settled; final approval filed 2026-10-30 | Case page |
| In re Otter.AI Privacy Litigation | N.D. Cal. 5:25-cv-06911-EKL | motion to dismiss granted in part, denied in part 2026-08-13 | Case page |
| White v. Mercor.io Corporation | N.D. Tex. 6:26-cv-00201-H | first amended complaint 2026-06-25; order on Mercor's motions entered 2026-11-12 (Dkt. 28) | Contributor lawsuits against human data platforms |
| noyb complaints against Scale AI (Outlier) | data protection authorities, five complaints | filed 2026-10-27 per noyb | Case page |
Contributor pay and classification suits, including White v. Mercor in Texas, are compared on the contributor lawsuits page.
More About the Mercor Data Breach Lawsuit
This page is information, not legal advice.
Decided Versus Still Open in the Mercor Breach Case
Only procedure is decided: the consolidation, the interim lead counsel and the stay; every claim, the classes and any payment are open.
- Decided: seven actions consolidated on 2026-05-19; interim lead counsel appointed; stay granted on 2026-07-21.
- Still open: Mercor's response to the complaint; the six counts; class certification; the mediation outcome and any settlement.
Frequently Asked Questions About the Mercor Data Breach Lawsuit
Is there one Mercor data breach lawsuit or several?
There is one: seven complaints were consolidated on 2026-05-19 under Lead Case No. 3:26-cv-02821-WHO.
Is there a Mercor data breach settlement or payout?
No settlement, payout or claim process is on the court record as of 2026-11-16. The case is stayed for mediation.
How do I join the Mercor class action?
No class is certified and no claim form exists on the record. The proposed class covers US residents whose data was accessed, including notice recipients; DataPacts gives no legal advice and offers no lookup.
Who represents the plaintiffs in the Mercor breach case?
The court appointed John J. Nelson of Milberg PLLC as interim lead counsel on 2026-05-19 (Dkt. 29). The order calls the appointment interim.
Did the breach expose company data licensed to Mercor?
No record read says so. The California Attorney General notice and the complaint describe the personal data of experts and applicants.