If you were affected, free legal review is available — no obligation.
Learn how to participate in the class action and what compensation you may be entitled to.
Join the Class Action →Use our verification tool to confirm your letter matches this official AG filing.
Verify My Notice LetterThis case file references a public filing made with the state filing in WA. This website is not affiliated with, endorsed by, or operated by any state government agency.
Mercor.io (LiteLLM) was the subject of a data breach notification filed with the WA Attorney General. The AG filing was recorded on June 26, 2026.
From the AG filing description
Mercor.io and its associated LiteLLM infrastructure operate at the critical intersection of modern artificial intelligence development, software deployment, and enterprise data processing. As a platform facilitating large language model integration, API routing, and automated workflow management, the company frequently handles immense volumes of proprietary corporate data, software developer credentials, system access logs, and internal enterprise communications. Because modern AI infrastructure requires deep integration into client networks to optimize machine learning pipelines and API calls, organizations like Mercor.io inherently accumulate vast repositories of sensitive digital assets, including proprietary source code, internal authentication tokens, API keys, and administrative credentials belonging to corporate clients and their end users. In 2026, reports surfaced regarding a significant security incident impacting Mercor.io and its LiteLLM ecosystem, which was subsequently reported to the Washington Attorney General. Breaches involving software platforms and AI infrastructure typically involve sophisticated cyberattacks such as unauthorized access to cloud-hosted databases, compromised API endpoints, third-party software supply chain vulnerabilities, or credential-stuffing attacks that bypass perimeter defenses. Given the interconnected nature of modern application programming interfaces, an intrusion into a service layer like LiteLLM can grant malicious actors deep visibility into underlying data streams, potentially exposing administrative controls and sensitive digital infrastructure to unauthorized external parties. When security incidents compromise platforms handling developer infrastructure and enterprise software integrations, the exposed data types routinely extend far beyond basic contact details. Victims of the Mercor.io breach may find their professional email addresses, password hashes, enterprise API keys, internal system credentials, session tokens, and administrative account details compromised. The exposure of API keys and credential hashes creates severe downstream security risks, as malicious actors can leverage stolen access tokens to hijack corporate accounts, infiltrate client cloud environments, inject malicious code into software pipelines, or execute unauthorized financial transactions. Furthermore, the compromise of administrative credentials opens the door to secondary targeted attacks, corporate espionage, and devastating ransomware deployments across the supply chain. As a technology provider operating in Washington state and processing enterprise digital assets, Mercor.io was bound by statutory and common-law duties of care to maintain robust, industry-standard cybersecurity measures. Under the Washington Data Breach Notification Act and the broader enforcement authority of the Federal Trade Commission Act, technology platforms holding sensitive digital credentials and corporate data are required to implement reasonable security safeguards, including multi-factor authentication, end-to-end encryption, continuous network monitoring, and rigorous vulnerability assessments. The occurrence of a data breach of this magnitude serves as a strong indicator that systemic security failures may have occurred, potentially breaching these statutory obligations and failing to protect sensitive digital infrastructure from foreseeable threats. Receiving a data breach notification letter from Mercor.io is a formal acknowledgement that your confidential information or account credentials were compromised as a result of corporate negligence. Legally, the receipt of this notice establishes the concrete standing required to participate in a class action lawsuit aimed at holding the company accountable for its security lapses. Under established legal principles, victims do not need to prove that financial fraud has already occurred to seek legal redress; the increased risk of identity theft, system compromise, and the time and expense required to remediate account security are actionable harms. Our law firm is currently investigating class action claims on behalf of affected individuals and entities on a contingency fee basis, meaning there are never any out-of-pocket costs or attorney fees unless we successfully recover compensation for you.
Under the Washington My Health MY Data Act, you may have a legal claim against Mercor.io (LiteLLM) if any of the following apply:
Common categories of compensation in data breach class actions
Courts recognize that the time spent monitoring accounts, placing credit freezes, and dealing with the aftermath of a breach has real economic value. This category of damages is recoverable even without direct financial loss.
When login credentials are exposed, the costs of downstream account compromises — password managers, security audits, and recovery costs for hijacked downstream accounts — can be recovered. Courts in recent class actions have awarded damages for credential exposure even without proven misuse.
Data breach victims regularly report anxiety, loss of sleep, and ongoing fear of identity theft. These non-economic harms are cognizable injuries in data breach litigation, particularly in cases involving SSN or medical record exposure.
Note: an attorney general breach filing does not by itself establish a settlement fund, a payment amount, or a claim deadline. If an official settlement notice is later issued, rely on that notice for payment details and deadlines.
No. Under Washington My Health MY Data Act and federal law, the unauthorized exposure of your personal data — regardless of whether it has been actively misused — can be sufficient grounds for a claim. The breach itself is the injury.
Nothing. The Law Office of David S. Harris handles data breach cases on contingency — you pay zero upfront and owe nothing unless compensation is recovered.
State statutes of limitations for data breach claims typically run 2–4 years from the date of the breach or its discovery. Because this breach was recently disclosed, the window is open — but acting early preserves your options and strengthens the case.
Accepting free credit monitoring from Mercor.io (LiteLLM) does not waive your right to pursue legal action unless you signed a specific release waiving claims. In most cases, victims who accepted monitoring can still file.
Not necessarily. Many data breach victims are never notified directly. If your personal information was held by Mercor.io (LiteLLM) during the relevant period, you may still qualify even without receiving a letter. A free eligibility review can confirm your status.
Most data breach class actions resolve within 18 to 36 months, though timelines vary by court and complexity. Your participation requires minimal effort — typically completing a claim form. Our office handles all litigation; you are notified when a settlement is reached.
Applicable State Law
This breach was reported under the Washington My Health MY Data Act, which mandates notification and establishes your right to seek damages.
Mercor.io (LiteLLM) breach?
Free case review · No fee unless you win