Clustered 6 filings across 6 jurisdictions · filing window Jun 1, 2026 → Jun 26, 2026. View entity profile → Other incidents for this victim →
incident inc_5b2d3634776648d5 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Government ID
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
CA IN MA NH TX VT
all State AG
per-filing reported counts
State AGs report only their own residents; bars show per-filing counts.
Earliest sighting first · deep chronology in Litigation Timeline
Mar 24, 2026 → Mar 30, 2026
When the intrusion reportedly occurred, per the linked filings
Mar 24, 2026
Reported by MASSACHUSETTS AG, NEW HAMPSHIRE AG filings
Mar 27, 2026
Reported by TEXAS AG filing
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.
Mercor.io Corporation notified Massachusetts residents of a data breach involving unauthorized access to systems via compromised LiteLLM code scanning tool malware. The incident occurred March 24-30, 2026, resulting in the exfiltration of personal information. Mercor offered 24 months of credit monitoring through TransUnion and enhanced security controls.
Mercor.io Corporation disclosed a data breach resulting from malware inserted into LiteLLM's code scanning tool, a third-party software supply chain compromise. The unauthorized actor accessed Mercor's systems between March 24 and March 30, 2026, and exfiltrated data. Mercor detected and blocked the activity, engaged third-party experts, and is offering 24 months of credit monitoring to affected individuals. The investigation is complete.
Mercor.io Corporation reported a data breach to the Vermont Attorney General. The breach was reported to the AGO on 2026-06-25. The reporting organization type is Other Commercial. 35 Vermont residents were affected. Categories of data breached: Social Security Numbers, Government ID Numbers.
Mercor.io Corporation reported a data breach to the Indiana Attorney General. The breach occurred on 2026-03-24 and was reported on 2026-06-25. 238 Indiana residents were affected. 21,677 individuals affected in total.
Affected (this filing): 21,677
Mercor.io Corporation notified the New Hampshire Attorney General of a security event involving the LiteLLM supply chain. An unauthorized actor exploited malware in LiteLLM code scanning tools to access Mercor's systems between March 24-30, 2026. The incident affected approximately 68 New Hampshire residents, exposing passport numbers, driver's license numbers, and other government IDs. Mercor engaged forensic investigators, notified law enforcement, and is offering 24 months of credit monitoring via TransUnion.
Affected (this filing): 68
Mercor.io Corporation based in San Francisco, California, a other entity reported a data breach to the Texas Attorney General. The breach was discovered on 2026-03-27 and reported on 2026-06-26. 2,025 Texas residents were affected. 21,677 individuals affected in total. Types of information involved: Name of individual;Address;Social Security Number Information;Driver’s License number;Government-issued ID number (e.g. passport, state ID card);Date of Birth. Consumers were notified via Email.
Affected (this filing): 2,025