{"schema_version":"0.10.0","id":"LR-2026-0313","record_version":1,"title":"Mercor breached through compromised LiteLLM PyPI releases (TeamPCP)","verification":{"human_verified":false,"method":"automated_gate","auto_verified":true,"score":51.3,"score_breakdown":{"source_authority":16.5,"independent_corroboration":7.0,"implicated_party_confirmed":0.0,"citation_integrity":14.0,"specificity":3.0,"completeness":3.2,"unhedged_language":5.0},"checks":{"schema_valid":true,"every_field_cited":true,"quotes_verbatim":true,"source_fetched":true,"distinct_incident":true,"dates_plausible":true,"sources_agree":true,"source_describes_incident":true,"severe_backed_by_source":true,"record_integrity":true,"eligible":true,"about_this_case":true},"gate_version":"gate-2026-10-18.7","cross_check_model":null,"cross_check_agreement":null,"duplicate_of":null,"verified_by":null,"verified_at":"2026-11-01","extraction_run_id":null,"evidence_level":{"level":"preliminary","reason":"Publisher not yet named · subject to change","original_document":null,"reports_total":1,"reports_independent":0,"reports_derivative":0,"developing":false,"disputed":false,"rules_version":"evidence-2026-10-29.1","computed_at":"2026-11-01","history":[{"date":"2026-11-01","from_level":null,"to_level":"preliminary","reason":"Publisher not yet named · subject to change"}]},"sources_hash":"72a4d0c1b51520b88d84e62689ca63bda552c1be0c0425ae2b8639b8c71685f3"},"system":{"model_name":null,"model_version":null,"developer":"unknown","harness":null,"tools_granted":[],"permissions_scope":null,"autonomy_level":"unknown","guardrails_present":[],"deployment_context":"unknown","tier":null,"lifecycle_stage":null,"integration_type":null,"intended_use":null,"safeguard_state":null,"production_intended":null},"event":{"date_occurred":"2026-03-01","date_occurred_precision":"month","date_disclosed":"2026-06-25","incident_class":"security_compromise","failure_class":null,"agent_involved":null,"secondary_failure_classes":[],"trigger":"unknown","duration":null,"detection_method":"unknown","summary":"Mercor, which works with AI experts and customers, was affected by a supply-chain attack involving LiteLLM, a commonly used open-source tool. A malicious actor published compromised versions of LiteLLM designed to exfiltrate credentials from any system that installed them. Mercor's security team determined that the company was affected during the relevant timeframe and took action to contain unauthorized activity. The company investigated with outside forensics experts and law enforcement. Of its nearly five million experts, only a very limited subset had sensitive information affected, and the company reported no evidence that this data had been used fraudulently. Notifications with identity protection offers were sent to affected individuals, and the company audited third-party dependencies and rotated credentials and access keys.","tags":[],"date_detected":null,"near_miss":null,"root_cause":null,"root_cause_detail":null,"failure_class_detail":null,"responsible_party":null,"adversarial_actor":null,"input_provenance":null,"time_to_contain":null,"operations_paused":null,"remediation":null,"precursor_events":null,"primary_risk":"RK06","secondary_risks":["RK03"]},"impact":{"direct_loss_usd":null,"remediation_hours":null,"records_exposed":null,"third_parties_affected_count":null,"severity":"moderate","severity_because":"Data of others touched (sensitive information of experts) with a bounded scope stated: only a very limited subset of nearly five million experts had sensitive information affected.","harm_class":[],"affected_description":null,"protected_class_involved":null,"data_categories_exposed":[],"loss_range_usd":null,"reversibility":null,"downstream_exposure_count":null},"evidence":{"sources":[{"url":"https://mercor.com/blog/update-on-mercor-security-incident/","publisher":"Mercor","date":"2026-06-25","type":"vendor_research","title":"Mercor Data Breach: Investigation Findings and Updates","archived_url":null,"attachment":"first_report"}],"per_field_confidence":{"event.date_occurred":"C","event.incident_class":"C","impact.severity":"D","impact.severity_because":"D","event.primary_risk":"D","event.secondary_risks":"D","event.summary":"C","system.autonomy_level":"D","system.deployment_context":"D","event.trigger":"D","event.detection_method":"D","context.country":"D","system.developer":"D","event.date_disclosed":"D","context.denominator_available":"D"},"field_citations":{"event.date_occurred":[{"source_index":0,"quote":"In late March 2026, Mercor was affected by a supply chain attack involving LiteLLM, a commonly used open-source tool."}],"event.incident_class":[{"source_index":0,"quote":"In March, a malicious actor published compromised versions of LiteLLM designed to exfiltrate credentials from any system that installed them."}],"impact.severity":[{"source_index":0,"quote":"Of our nearly five million experts, only a very limited subset had sensitive information affected."}],"impact.severity_because":[{"source_index":0,"quote":"Of our nearly five million experts, only a very limited subset had sensitive information affected."}],"event.summary":[{"source_index":0,"quote":"In late March 2026, Mercor was affected by a supply chain attack involving LiteLLM, a commonly used open-source tool."},{"source_index":0,"quote":"In March, a malicious actor published compromised versions of LiteLLM designed to exfiltrate credentials from any system that installed them."},{"source_index":0,"quote":"Our security team determined that Mercor was affected during the relevant timeframe and immediately took action to contain unauthorized activity."},{"source_index":0,"quote":"Of our nearly five million experts, only a very limited subset had sensitive information affected."},{"source_index":0,"quote":"There is no evidence that any of this data has been used fraudulently."},{"source_index":0,"quote":"The notifications will include details about the type of information affected along with an offer of TransUnion identity protection services."}]},"notes_on_gaps":"The sources describe a supply-chain compromise of the LiteLLM open-source package; no AI model, agent, or autonomous action is stated, so system fields, agent_involved, and failure_class are left out. Only one source (Mercor's own update) was provided. Its date of 2026-06-25 is taken from the source header and used as the disclosure date, a judgement made by me. The sources do not state the detection method, the root cause category, the trigger, the adversary's origin, records or party counts, financial loss, containment duration, or whether any specific control held or failed during the incident, so these are left out and no link entries are made. The severity of moderate rests on the stated privacy impact to a bounded subset of experts; the sources give no count of affected companies. Mercor's remediation list is taken from its own statements; the mapping of each measure to a control ID is my judgement. The phrase 'a significant number of companies' is not a stated count and was not used as a value. [case created by the backfill: read by claude-haiku-5-5, backfill-2026-11-01.2, 2026-11-01; not yet reviewed] [2026-11-01: evidence level set: Preliminary (Publisher not yet named · subject to change)]"},"context":{"industry":null,"org_size_band":null,"country":"unknown","denominator_available":false,"denominator":null,"related_incident_ids":[],"systemic_exposure":null,"shared_model_id":null,"upstream_incident_id":null,"incident_evidence":null,"regulatory":null,"coverage":null},"narrative":{"steps":[{"step":"doing","text":"Mercor relied on LiteLLM, a commonly used open-source tool, when a supply-chain attack involving it reached the company.","quote":"In late March 2026, Mercor was affected by a supply chain attack involving LiteLLM, a commonly used open-source tool.","source_index":0,"grade":"C"},{"step":"went_wrong","text":"A malicious actor published compromised LiteLLM versions designed to exfiltrate credentials from any system that installed them.","quote":"In March, a malicious actor published compromised versions of LiteLLM designed to exfiltrate credentials from any system that installed them.","source_index":0,"grade":"C"},{"step":"reached","text":"Of nearly five million experts, only a very limited subset had sensitive information affected.","quote":"Of our nearly five million experts, only a very limited subset had sensitive information affected.","source_index":0,"grade":"C"},{"step":"caught","text":"Mercor's security team determined it was affected and immediately acted to contain unauthorized activity.","quote":"Our security team determined that Mercor was affected during the relevant timeframe and immediately took action to contain unauthorized activity.","source_index":0,"grade":"C"}],"model":"claude-haiku-5-5","prompt_version":"backfill-2026-11-01.2","extracted_at":"2026-11-01","source_urls":["https://mercor.com/blog/update-on-mercor-security-incident/"]},"analysis":{"sections":{"timeline":[{"text":"Mercor was affected by a supply-chain attack involving LiteLLM.","quote":"In late March 2026, Mercor was affected by a supply chain attack involving LiteLLM, a commonly used open-source tool.","source_index":0,"when":"late March 2026"},{"text":"A malicious actor published compromised LiteLLM versions designed to exfiltrate credentials.","quote":"In March, a malicious actor published compromised versions of LiteLLM designed to exfiltrate credentials from any system that installed them.","source_index":0,"when":"March"},{"text":"Mercor's security team determined it was affected and immediately acted to contain unauthorized activity.","quote":"Our security team determined that Mercor was affected during the relevant timeframe and immediately took action to contain unauthorized activity.","source_index":0,"when":null},{"text":"Mercor worked with outside forensics experts, industry peers and law enforcement during the investigation.","quote":"We worked with leading industry experts including Google’s Mandiant, Latacora, industry peers, and law enforcement to investigate and take appropriate action.","source_index":0,"when":null},{"text":"The investigation was completed.","quote":"That investigation is now complete.","source_index":0,"when":null},{"text":"Mercor began notifying affected experts directly.","quote":"We are in the process of notifying these individuals directly on June 25 and June 26 from [email protected].","source_index":0,"when":"June 25 and June 26"}]},"model":"claude-haiku-5-5","prompt_version":"backfill-2026-11-01.2","extracted_at":"2026-11-01","source_urls":["https://mercor.com/blog/update-on-mercor-security-incident/"]}}