--- title: "Press Releases" description: "Browse MercorClaims press releases, newsroom announcements, and source-backed updates in one searchable archive." canonical_url: "https://alpha.mercor.instalaw.io/press" last_updated: "2026-04-02" --- # MercorClaims newsroom, announcements, and press releases. The MercorClaims press room is the public archive for press releases, launch announcements, and editorial notices tied to the site's Mercor breach coverage — dated, cited, and kept on the record. ## Newsroom standards - Each release receives a permanent URL so it can be cited, shared, and indexed on its own merits. - Every entry is paired with descriptive metadata, structured data, and a markdown mirror for agents and researchers. - New releases are added to the archive by extending the typed newsroom content collection — no CMS, no silent edits. - Corrections are published openly, dated, and left visible. We don't retouch the record. ## Latest release [MercorClaims opens the public archive of Mercor breach material](/press/mercorclaims-opens-public-archive) ## Archive ## MercorClaims opens the public archive of Mercor breach material **Category:** Site Launch **Published:** April 16, 2026 **Permalink:** [/press/mercorclaims-opens-public-archive](/press/mercorclaims-opens-public-archive) MercorClaims opened its public archive on April 16, 2026, bringing together the email notices, press reports, and public statements that together form the first full record of the Mercor incident. ### Highlights - Every entry is tied to a citable public source. - The archive is free to read — no accounts, no trackers, no advertising. - Readers can submit new sources; every addition is dated before it is posted. ### Why this archive exists Breach coverage is scattered across news stories, notice emails, policy pages, and social posts. MercorClaims pulls that material into one archive so visitors can read the record rather than piece it together. The archive is independent of Mercor and is not a law firm. Its only job is to make it easier to understand what has, and has not, been confirmed. - A single place to read what's public - Dated entries, each tied to a source - No ads, no accounts, no tracking to read ### How entries are written Every entry links back to the public source it came from — an email screenshot, a news article, a policy page, a filing. Readers can open the original material and judge it for themselves. Corrections are published openly, dated, and left visible. The archive is meant to hold up over time, not to flatter anyone. ### What gets added next Future entries will cover newly published source material, court filings, meaningful editorial notes, and other public-facing developments that change what is known about the Mercor incident. - Notices and filings as they become public - New reporting from outlets covering the incident - Editorial notes about the archive itself ### About MercorClaims MercorClaims is an informational website focused on helping visitors follow the Mercor data breach through publicly available information, source material, and future AI-assisted tools. MercorClaims is not a law firm and does not provide legal advice. ## MercorClaims publishes an analysis of Mercor's email notice to affected people **Category:** Editorial Notice **Published:** April 12, 2026 **Permalink:** [/press/mercorclaims-publishes-email-notice-analysis](/press/mercorclaims-publishes-email-notice-analysis) MercorClaims has published a dedicated archive entry breaking down the email notice Mercor sent to affected people — what it confirms, what it leaves open, and where it sits in the broader timeline. ### Highlights - Annotates Mercor's own words to affected people. - Pairs the notice with a recreated screenshot shared with MercorClaims. - Separates what the notice confirms from what it leaves open. ### A direct source, read closely The email notice is the first direct communication from Mercor to affected people that MercorClaims has been able to cite. Treating it carefully matters: small phrases change what the document is, and isn't, evidence for. The analysis walks through the notice paragraph by paragraph, separating what Mercor affirmatively confirms from what it defers — for example, the categories of data involved, which the notice explicitly declines to describe while the investigation is open. ### What the notice confirms Taken on its face, the notice establishes that Mercor identified a security incident, took steps to secure its systems, opened an investigation, and engaged third-party forensic experts. - An incident occurred and was identified by Mercor. - Mercor says it moved promptly to contain and remediate. - Third-party forensic experts are assisting. - Further detail is being withheld while the investigation is active. ### What it does not decide The notice does not, on its own, establish the scope of data accessed or exfiltrated, the identity of the threat actor, or whether any specific person's information was involved. Those questions remain open and will move as new source material becomes available. ### About MercorClaims MercorClaims is an informational website focused on helping visitors follow the Mercor data breach through publicly available information, source material, and future AI-assisted tools. MercorClaims is not a law firm and does not provide legal advice. ## MercorClaims timeline ties the Mercor incident to the LiteLLM compromise **Category:** Investigation **Published:** April 6, 2026 **Permalink:** [/press/mercorclaims-timeline-links-incident-to-litellm](/press/mercorclaims-timeline-links-incident-to-litellm) MercorClaims has published a dated timeline placing the Mercor incident next to the underlying compromise of the open-source LiteLLM project, citing TechCrunch's March 31, 2026 reporting and Mercor's own statements. ### Highlights - Anchors the Mercor incident to the LiteLLM compromise using public reporting. - Places Mercor's own statements next to outside confirmation, on one dated timeline. - Sets up readers to evaluate follow-on disclosures from other organizations downstream of LiteLLM. ### Moving from “a breach” to “a supply-chain breach” Early coverage of the incident framed it as a Mercor-specific event. Public reporting, most prominently by TechCrunch on March 31, 2026, reframed it: Mercor was affected as part of a broader compromise of the open-source LiteLLM project used by many organizations in the AI industry. The timeline makes that link readable. Each entry carries a date and a citation, so readers can see when the narrative shifted and on what evidence. ### Why the LiteLLM link matters LiteLLM is infrastructure glue: a proxy and library that sits between applications and large-language-model providers. A compromise of that kind of component doesn't stop at one company — it reaches every organization that uses it. Reading the Mercor incident through that lens changes what readers should expect next: more organizations may be drawn into the story, not fewer. - The upstream cause is outside Mercor's codebase. - Other organizations that rely on LiteLLM may surface disclosures of their own. - Attribution and scope are still moving as reporting continues. ### About MercorClaims MercorClaims is an informational website focused on helping visitors follow the Mercor data breach through publicly available information, source material, and future AI-assisted tools. MercorClaims is not a law firm and does not provide legal advice. ## MercorClaims launches a newsroom for source-backed breach updates and future announcements **Category:** Company News **Published:** April 2, 2026 **Permalink:** [/press/mercorclaims-launches-newsroom](/press/mercorclaims-launches-newsroom) MercorClaims has launched a dedicated newsroom to centralize press releases, public-facing site announcements, and future editorial updates tied to Mercor breach coverage. ### Highlights - A dedicated `/press` archive now organizes current and future newsroom entries. - Each release is published as a standalone page with canonical metadata and structured data. - Markdown mirrors make the newsroom easier to index, quote, and process programmatically. ### A dedicated archive for future announcements MercorClaims has launched a newsroom at `/press` to centralize future press releases and official site announcements related to the Mercor breach. The archive is designed to give reporters, researchers, and affected visitors a stable place to find high-signal announcements without having to piece them together from the broader site. - Permanent URLs for every release - A browsable archive page for newsroom discovery - Machine-readable markdown mirrors for downstream indexing ### Built to support search visibility and citation Each newsroom entry is published as a standalone page with descriptive metadata, a canonical URL, and structured data so search engines can understand the page as a first-class release rather than a generic site update. This structure also makes the archive easier to cite in reporting, easier to revisit later, and easier for AI systems to parse accurately. ### What future releases will cover Future newsroom entries may cover newly published source material, site feature launches, meaningful editorial updates, or other public-facing developments that affect how MercorClaims presents breach information. The newsroom sits alongside the broader updates archive so official announcements and source-backed notices can work together without being mixed into a single undifferentiated feed. - Launches and product updates - Editorial notes about the archive or source material - New public-facing announcements relevant to site visitors ### About MercorClaims MercorClaims is an informational website focused on helping visitors follow the Mercor data breach through publicly available information, source material, and future AI-assisted tools. MercorClaims is not a law firm and does not provide legal advice. ## Boilerplate MercorClaims is an informational website focused on helping visitors follow the Mercor data breach through publicly available information, source material, and future AI-assisted tools. MercorClaims is not a law firm and does not provide legal advice. ## Sitemap See the full [sitemap](/sitemap.md) for all pages.