DataBreachRecords.com

Record REC-WA-2026-12563

Breach Record: Mercor.io (LiteLLM)

One row in the registry of breaches filed with Washington. Fields with no value in the filing are left blank.

Record fields

Entity
Mercor.io (LiteLLM)
Jurisdiction
Washington
Agency
Washington Attorney General
Date filed
June 26, 2026
Data fields
Full Name; Email Address; Password or Credential Hash; API Keys and Access Tokens; Administrative Credentials; Mailing Address; Internal System Logs; Payment Card Information
Washington breach records

Abstract

Mercor.io, also known for its LiteLLM infrastructure, officially notified the Washington Attorney General about a security incident on June 26, 2026. The company operates at the critical intersection of artificial intelligence development and enterprise data processing, facilitating large language model integration and automated workflow management. The specific nature of the breach was not disclosed in public records, but the company indicated an impact on sensitive information.

Platforms like Mercor.io frequently handle substantial volumes of proprietary corporate data, software developer credentials, system access logs, and internal enterprise communications. Given its role in AI infrastructure and API routing, an intrusion can grant unauthorized parties deep access to data streams and underlying digital assets.

The reported exposed data types include Full Name, Email Address, Password or Credential Hash, API Keys and Access Tokens, Administrative Credentials, Mailing Address, Internal System Logs, and Payment Card Information. The compromise of items such as API keys and administrative credentials can create significant downstream security risks, potentially allowing malicious actors to access linked corporate accounts or systems.

Individuals who receive a data breach notification from Mercor.io should promptly change affected passwords and enable multi-factor authentication on all online accounts, especially those linked to their professional identity. It is also advisable to monitor financial statements and credit reports for any unusual activity. Reviewing access logs for critical systems or developer accounts for unauthorized entries is another crucial step.

While the full scope of the breach and the number of affected individuals remain unspecified in publicly available information, the presence of such sensitive data types warrants immediate protective measures by those impacted.

Record notes

What is the reference number?
A registry identifier built from the state, the filing year and the record ID. It never changes.
Why is a field blank?
The state did not publish that value. Blank fields are not filled in by estimate.
Can one breach have several records?
Yes. A company that notifies several states has one record per state filing.
How are related records chosen?
They are other breaches filed in the same state, newest first.

Agency source: Washington Attorney General