Mercor.io (LiteLLM) data breach
Incident readout
- Company
- Mercor.io (LiteLLM)
- Reported to
- Washington Attorney General
- Filed
- June 26, 2026
- People affected
- Not stated in the filing
- Incident type in filing
- Not stated
- Our review
- Monitoring
Was this a ransomware attack?
The filing does not say ransomware was involved. We do not label an incident ransomware unless the company’s report says so. Whatever the cause, the steps to protect yourself and the legal question are the same.
Information listed in the filing
- Full Name
- Email Address
- Password or Credential Hash
- API Keys and Access Tokens
- Administrative Credentials
- Mailing Address
- Internal System Logs
- Payment Card Information
What we know
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.
See every breach reported in Washington or read what to do after a ransomware attack.
After the Mercor.io incident: what to do and your options
- What should I do after getting the Mercor.io data breach notice?
- Keep the letter and the envelope, and note the date it arrived. Freeze your credit with Equifax, Experian and TransUnion, change any passwords the notice mentions, and sign up for any free credit monitoring the letter offers. Then check whether you may have a claim.
- How many people were affected by the Mercor.io data breach, and what was exposed?
- The filing does not give a count of affected people and lists the following information as involved: Full Name, Email Address, Password or Credential Hash, API Keys and Access Tokens, Administrative Credentials, Mailing Address, Internal System Logs, Payment Card Information. Your own letter is the best guide to what was exposed about you, since notices are usually tailored to each person.
- Did Mercor.io offer free credit monitoring?
- Look for an enrollment code in your Mercor.io notice. Companies that offer free credit monitoring after a breach usually include it there, with a deadline to activate. Because financial or account details are listed in this filing, watch your bank and card statements closely as well. Using the free service won't stop you from joining a lawsuit or settlement later.
- Where can I see the official Mercor.io breach notice?
- Mercor.io's report is published by the Washington Attorney General: https://agportal-s3bucket.s3.amazonaws.com/databreach/BreachM24486.pdf Compare it with the letter you received to confirm the dates and details match.
- Can I sue Mercor.io over the data breach?
- It depends on what was exposed, the law in Washington and your own state, and whether you've been harmed. Most people take part through a class action rather than suing alone. Keep your notification letter — it's the proof that connects you to the breach.
- Do I need a Mercor.io data breach lawyer or attorney?
- Whether the company's systems were encrypted by ransomware or data was simply taken, the legal question is the same: did it protect your information the way the law requires? An attorney can review your notice for free, and these cases are usually handled on contingency.
- Is there a Mercor.io data breach class action lawsuit?
- Law firms often open an investigation after a breach notice like this one, and a class action lawsuit may follow. This page doesn't confirm that a lawsuit has been filed against Mercor.io. You usually don't have to join a class action to be included — if a settlement is reached, class members are notified and can file a claim.
- Is the Mercor.io data breach letter legit or a scam?
- A notice from Mercor.io in the mail matches the breach Mercor.io reported to the Washington Attorney General on June 26, 2026. Check that the company name and dates in your letter match that filing. A real notice of data security incident won't ask for your password, Social Security number or a payment — if it does, contact Mercor.io through a phone number or website you find yourself.
- How much could a Mercor.io data breach settlement or claim be worth?
- There is no set amount, and no Mercor.io settlement is confirmed here. In past data breach settlements, payments depended on what data was exposed and on documented losses — fraud, out-of-pocket costs and time spent dealing with the breach. The filing lists Full Name, Email Address, Password or Credential Hash as involved. Keep receipts and records; they're what damages claims are built on.
Other breaches reported in Washington
- iRhythm Technologies Inc.Washington Attorney General · Filed October 6, 2026Count not stated
- Poppins Payroll CompanyWashington Attorney General · Filed September 29, 2026Count not stated
- zHealth, Inc.Washington Attorney General · Filed September 11, 2026Count not stated
- Cornerstone Staffing Solutions, Inc.Washington Attorney General · Filed September 11, 2026Count not stated
- Quatrro Business Support Services, Inc.Washington Attorney General · Filed September 9, 2026Count not stated
- Hibbett Retail, Inc.Washington Attorney General · Filed September 8, 2026Count not stated
Attorney advertising. This page reflects a public regulator filing; it does not mean a lawsuit has been filed or that the company did anything unlawful. Submitting a review request does not create an attorney-client relationship.