In short: Meta has suspended its collaboration with Mercor, a $10 billion AI data startup, after a supply chain attack exposed what may be the AI industry’s most closely guarded secrets: not just personal data, but the training methodologies that power the world’s leading large language models. The breach, carried out via a poisoned version of the LiteLLM open-source library, has triggered investigations at OpenAI and Anthropic, and resulted in a class action lawsuit affecting more than 40,000 people.

When hackers poisoned a widely used open-source library last month, they did not just steal personal data. According to reporting by Wired, they may have walked out with the blueprints for how some of the world’s most powerful AI models are built.

Meta has paused its work with Mercor, a San Francisco-based AI data company that generates bespoke training datasets for the biggest names in artificial intelligence, after a cyberattack exposed sensitive information about how the company, and potentially several of its other clients, actually trains its models. The pause is indefinite, and the incident has sent a ripple of anxiety through an industry that has spent billions developing the proprietary methods it was counting on keeping secret.

The startup behind the curtain

Mercor is not a household name, but it sits at a critical juncture of the AI economy. Founded in 2023 by Brendan Foody, Adarsh Hiremath, and Surya Midha, three Bay Area high school friends who competed together on the Bellarmine College Preparatory Speech and Debate team, the company recruits networks of human contractors, engineers, lawyers, doctors, bankers, and journalists, to produce high-quality, proprietary training data for AI labs. Its clients have included Meta, OpenAI, Anthropic, and Google.

The startup’s rise has been extraordinary even by Silicon Valley standards. In October 2025, Mercor closed a $350 million Series C round that valued it at $10 billion, minting all three founders as the world’s youngest self-made billionaires at the age of 22. By September 2025, the company had reached $500 million in annualised revenue, up from $100 million just six months earlier. Its business model, generating the fine-tuning and reinforcement learning data that AI labs rely on but rarely discuss publicly, made it one of the most valuable private companies in the AI supply chain.

That same positioning is now the source of its vulnerability.

A poisoned package, a cascade of exposure

The attack that reached Mercor originated several steps upstream. According to analysis by Wiz, Snyk, and Datadog Security Labs, a threat actor group known as TeamPCP compromised the CI/CD pipeline of LiteLLM, an open-source Python library used by millions of developers to connect applications to AI services, with 97 million monthly downloads and a presence in an estimated 36% of cloud environments.

TeamPCP had earlier used a supply chain attack on Trivy, a widely used security scanner, to obtain credentials belonging to a LiteLLM maintainer. On 27 March 2026, the group used those credentials to publish two malicious versions of the LiteLLM package, 1.82.7 and 1.82.8, directly to PyPI, the Python package repository. The tainted packages were available for roughly 40 minutes before being identified and removed.

The payload was sophisticated. Version 1.82.7 embedded base64-encoded malware directly into the library’s proxy server code, executing on import. Version 1.82.8 used a malicious path configuration file that triggered automatically on every Python process startup. Both variants were designed to harvest environment variables, API keys, SSH keys, cloud credentials across AWS, Google Cloud, and Azure, Kubernetes configurations, CI/CD secrets, and database credentials, exfiltrating everything to a server at models.litellm[.]cloud.

Mercor, which confirmed it was “one of thousands of companies” affected by the attack, subsequently found that the breach had exposed approximately four terabytes of data. According to court filings and claims made by the hacking groups involved, the stolen cache includes 939 gigabytes of platform source code, a 211-gigabyte user database, and roughly three terabytes of video interview recordings and identity verification documents. The exposed information may include the full names and Social Security numbers of more than 40,000 current and former Mercor contractors and customers.

The secrets that matter most

The personal data exposure would be troubling enough. But what has alarmed Meta and drawn the attention of other AI labs is a different category of information entirely.

Because Mercor sits inside the data pipelines of multiple AI companies simultaneously, the breach may have exposed details about data selection criteria, labeling protocols, and training strategies that companies have spent years and billions of dollars developing. Competitors can replicate a dataset; replicating a training methodology is harder, and it represents a genuine competitive moat. The Wired report notes that the scale of that potential exposure has prompted multiple AI labs to investigate what, precisely, may have left their orbit.

OpenAI, which also uses Mercor’s services, has said it is investigating the incident but has not paused its current projects with the company. Anthropic, which raised $3 billion in early 2026 and has been expanding its research infrastructure aggressively, has not publicly commented on its exposure. Google, which operates competing data vendor relationships of a similar kind, is also understood to be assessing the breach’s scope.

The incident illustrates a structural risk that the AI industry has rarely had to confront: when multiple competitors rely on the same third-party data supplier, a single breach can expose the competitive secrets of all of them at once.

Extortion and legal fallout

The threat group Lapsus$, which has previously been linked to high-profile attacks on major corporations, subsequently claimed responsibility for the Mercor breach and began auctioning the stolen data on dark web forums. Security researchers believe Lapsus$ is acting in collaboration with TeamPCP, which has emerged as a systematic threat across the AI and enterprise software ecosystem. The same group is believed responsible for a wave of supply chain compromises affecting more than 1,000 enterprise SaaS environments via the earlier Trivy attack, including a breach of the European Commission attributed by CERT-EU to the same campaign.

On 1 April 2026, plaintiff Lisa Gill, a resident of Wahiawa, Hawaii, filed a class action complaint against Mercor.io Corp. in the US District Court for the Northern District of California. The suit alleges that Mercor failed to maintain adequate cybersecurity protections, leaving more than 40,000 people exposed to identity theft and fraud. The complaint states that the LiteLLM incident on 27 March was the entry point and that Mercor’s reliance on a compromised open-source dependency without sufficient monitoring created the conditions for the breach.

Meta, meanwhile, has said nothing publicly, a silence that speaks volumes. The company signed a $27 billion AI infrastructure deal with Nebius Group in March 2026 and has forecast capital expenditures of between $115 billion and $135 billion for the year, making its AI training pipeline one of its most strategically sensitive assets. Pausing a data vendor relationship, even an important one, is the kind of decision that gets made only when the risk to proprietary methodology outweighs the operational cost of stopping work.

A cautionary tale for the AI supply chain

The Mercor breach is, in one sense, a conventional supply chain attack: a threat actor found a weak link in an open-source dependency and exploited it for credential theft and data exfiltration. In another sense, it is something newer and more unsettling. The AI industry has built its most valuable intellectual property on top of an interconnected web of data vendors, open-source tools, and shared infrastructure, and that web now constitutes an attack surface that no single company fully controls.

Security companies have been warning about precisely this dynamic. Aikido Security, which reached unicorn status in January 2026, built its business on the premise that open-source dependency risk had become existential for enterprise software. The Mercor incident suggests the same logic applies, perhaps more acutely, to the AI training pipeline.

For the three young founders who built one of the fastest-growing companies in tech, the coming months will test whether Mercor’s extraordinary momentum can survive a breach that exposed not just its users’ data, but its clients’ most carefully guarded secrets. The AI industry’s breakneck 2025 was built on the assumption that the infrastructure underpinning it was secure enough to trust. That assumption is now under review.

For the last couple of years, Microsoft has been all-in on Copilot. It’s literally everywhere, be it Windows, Edge, Office, or even baked into core workflows where you can’t really ignore it. The messaging has been clear: this is the future of productivity, your AI assistant for getting real work done.

And now, suddenly, Microsoft is saying… don’t take it too seriously.

Microsoft is walking back Copilot’s “serious use” pitch

As reported first by Tom’s Hardware, the Microsoft Copilot Terms of Use state that Copilot is intended for “entertainment purposes only” and shouldn’t be relied on for important or high-stakes decisions. That includes things like financial, legal, or medical advice. Basically, the kind of stuff people are increasingly using AI for.

Copilot is for entertainment purposes only. It can make mistakes, and it may not work as intended. Don’t rely on Copilot for important advice. Use Copilot at your own risk.

On paper, this makes sense. AI can hallucinate, get things wrong, and occasionally sound far more confident than it should. From a legal standpoint, this disclaimer is almost expected, as it acts like a safety net to avoid potential liability as these tools scale.

But here’s where it starts to feel a bit off. This is the same Copilot Microsoft has deeply integrated into Word, Excel, Outlook, and Teams. In fact, they’re even baked into Microsoft’s own Enterprise solutions, as pointed out by users. Tools that people use for actual work, not casual experimentation. When your AI is summarizing emails, drafting reports, or analyzing data, calling it “entertainment” feels oddly out of sync with reality.

The internet isn’t exactly buying it

Unsurprisingly, the internet isn’t exactly applauding. The reaction has mostly been confusion mixed with plenty of eye-rolls. Because let’s be honest, if Copilot isn’t meant for serious use, why is it sitting front and center inside tools people rely on to do serious work?

It’s starting to feel less like a redefinition and more like a safety net. Push Copilot everywhere, make it unavoidable, sell it as the future, and then quietly add a “don’t rely on it” label when things get complicated. It’s a neat way to enjoy the upside of AI while sidestepping the responsibility that comes with it.

Now, sure, Microsoft isn’t alone here. Every AI tool comes with some version of this disclaimer buried in the fine print. But most of those tools are optional. You install them, you try them out, and you decide how much to trust them. Unfortunately, Copilot did not follow that route. It showed up across Windows and Office and made itself part of the experience, whether you asked for it or not.

Standing desks have gone from being niche ergonomic upgrades to mainstream workspace essentials, driven by growing awareness of the risks associated with long, uninterrupted hours of sitting.

Alternating between sitting and standing throughout the day can help reduce back strain, improve posture, and encourage better circulation, while also helping users stay more alert during extended work sessions. For many people working from home, the standing desk has become a central part of creating a healthier, more flexible workspace.