Hackers Claim to Be Selling Mistral AI Source Code for $25K: What We Know
A hacker account linked to TeamPCP claims to be selling about 5GB of internal Mistral AI repositories for $25,000, but there is no public proof the data is real, and Mistral says its infrastructure was not breached du... The claim surfaced days after the Mini Shai‑Hulud campaign compromised more than 170 npm and PyP...
Published byEdited with GPT-5.5Images generated with GPT Image 2
A hacker account linked to TeamPCP claims to be selling about 5GB of internal Mistral AI repositories for $25,000, but there is no public proof the data is real, and Mistral says its infrastructure was not breached du...
The claim surfaced days after the Mini Shai‑Hulud campaign compromised more than 170 npm and PyPI packages, including Mistral AI SDK releases.
Security researchers say the alleged leak could stem from stolen developer credentials or simply be opportunistic fraud exploiting publicity around the attack.
What do we know about the reported claim that hackers linked to TeamPCP are selling Mistral AI source code for $25,000, including what dataReports claim hackers linked to TeamPCP are selling alleged Mistral AI repositories after a supply‑chain attack, though the authenticity of the data has not been verified.
AI Prompt
Create a landscape editorial hero image for this Studio Global article: What do we know about the reported claim that hackers linked to TeamPCP are selling Mistral AI source code for $25,000, including what data. Article summary: The claim is reported but not verified: a TeamPCP-linked forum account allegedly offered “Mistral AI repositories” for $25,000, but there is no public proof that the files are genuine or that Mistral AI’s core infrastruc. Topic tags: general, documentation, general web, user generated, education. Reference image context from search candidates: Reference image 1: visual subject "Square profile picture" source context "VECERT Analyzer on X: "🚨 🤖 CYBER INTELLIGENCE ALERT: POSSIBLE SOURCE CODE LEAK - MISTRAL AI ⚠️ EXPOSURE OF INTERNAL RE" Reference image 2: visual subject "The image shows a screenshot of a healthcare portal's user interface in which a user accesse
openai.com
Reports circulating in security forums claim that hackers linked to the group TeamPCP are attempting to sell internal Mistral AI repositories for $25,000. The offer appeared shortly after a major software supply‑chain attack affected Mistral’s SDK packages.
However, the available evidence does not confirm that any genuine Mistral source code has been stolen or leaked. The claim currently rests on a forum post with no independent verification.
The Alleged Sale of Mistral AI Repositories
Security reporting indicates that a forum account associated with the TeamPCP threat group advertised roughly 5GB of files described as internal Mistral AI repositories, priced at $25,000. The listing claimed the material was related to AI training and inference projects.
Important details remain unclear:
The files are described only as “repositories,” not confirmed model weights or production systems.
There is no public evidence showing the contents of the files.
No cryptographic verification or repository history has been provided.
Because of this lack of proof, the claim currently remains unverified.
The Context: The Mini Shai‑Hulud Supply‑Chain Attack
The alleged sale surfaced days after the Mini Shai‑Hulud campaign, a coordinated supply‑chain attack attributed to TeamPCP that compromised more than 170 packages across npm and PyPI ecosystems.
Studio Global AI
Continue your research
This page includes a source-backed answer you can continue inside Studio Global.
What is the short answer to "Hackers Claim to Be Selling Mistral AI Source Code for $25K: What We Know"?
A hacker account linked to TeamPCP claims to be selling about 5GB of internal Mistral AI repositories for $25,000, but there is no public proof the data is real, and Mistral says its infrastructure was not breached du...
What are the key points to validate first?
A hacker account linked to TeamPCP claims to be selling about 5GB of internal Mistral AI repositories for $25,000, but there is no public proof the data is real, and Mistral says its infrastructure was not breached du... The claim surfaced days after the Mini Shai‑Hulud campaign compromised more than 170 npm and PyPI packages, including Mistral AI SDK releases.
What should I do next in practice?
Security researchers say the alleged leak could stem from stolen developer credentials or simply be opportunistic fraud exploiting publicity around the attack.
Hackers Claim to Be Selling Mistral AI Source Code for $25K: What We Know
A hacker account linked to TeamPCP claims to be selling about 5GB of internal Mistral AI repositories for $25,000, but there is no public proof the data is real, and Mistral says its infrastructure was not breached du... The claim surfaced days after the Mini Shai‑Hulud campaign compromised more than 170 npm and PyP...
Published byEdited with GPT-5.5Images generated with GPT Image 2
A hacker account linked to TeamPCP claims to be selling about 5GB of internal Mistral AI repositories for $25,000, but there is no public proof the data is real, and Mistral says its infrastructure was not breached du...
The claim surfaced days after the Mini Shai‑Hulud campaign compromised more than 170 npm and PyPI packages, including Mistral AI SDK releases.
Security researchers say the alleged leak could stem from stolen developer credentials or simply be opportunistic fraud exploiting publicity around the attack.
What do we know about the reported claim that hackers linked to TeamPCP are selling Mistral AI source code for $25,000, including what dataReports claim hackers linked to TeamPCP are selling alleged Mistral AI repositories after a supply‑chain attack, though the authenticity of the data has not been verified.
AI Prompt
Create a landscape editorial hero image for this Studio Global article: What do we know about the reported claim that hackers linked to TeamPCP are selling Mistral AI source code for $25,000, including what data. Article summary: The claim is reported but not verified: a TeamPCP-linked forum account allegedly offered “Mistral AI repositories” for $25,000, but there is no public proof that the files are genuine or that Mistral AI’s core infrastruc. Topic tags: general, documentation, general web, user generated, education. Reference image context from search candidates: Reference image 1: visual subject "Square profile picture" source context "VECERT Analyzer on X: "🚨 🤖 CYBER INTELLIGENCE ALERT: POSSIBLE SOURCE CODE LEAK - MISTRAL AI ⚠️ EXPOSURE OF INTERNAL RE" Reference image 2: visual subject "The image shows a screenshot of a healthcare portal's user interface in which a user accesse
openai.com
Reports circulating in security forums claim that hackers linked to the group TeamPCP are attempting to sell internal Mistral AI repositories for $25,000. The offer appeared shortly after a major software supply‑chain attack affected Mistral’s SDK packages.
However, the available evidence does not confirm that any genuine Mistral source code has been stolen or leaked. The claim currently rests on a forum post with no independent verification.
The Alleged Sale of Mistral AI Repositories
Security reporting indicates that a forum account associated with the TeamPCP threat group advertised roughly 5GB of files described as internal Mistral AI repositories, priced at $25,000. The listing claimed the material was related to AI training and inference projects.
Important details remain unclear:
The files are described only as “repositories,” not confirmed model weights or production systems.
There is no public evidence showing the contents of the files.
No cryptographic verification or repository history has been provided.
Because of this lack of proof, the claim currently remains unverified.
The Context: The Mini Shai‑Hulud Supply‑Chain Attack
The alleged sale surfaced days after the Mini Shai‑Hulud campaign, a coordinated supply‑chain attack attributed to TeamPCP that compromised more than 170 packages across npm and PyPI ecosystems.
Studio Global AI
Continue your research
This page includes a source-backed answer you can continue inside Studio Global.
What is the short answer to "Hackers Claim to Be Selling Mistral AI Source Code for $25K: What We Know"?
A hacker account linked to TeamPCP claims to be selling about 5GB of internal Mistral AI repositories for $25,000, but there is no public proof the data is real, and Mistral says its infrastructure was not breached du...
What are the key points to validate first?
A hacker account linked to TeamPCP claims to be selling about 5GB of internal Mistral AI repositories for $25,000, but there is no public proof the data is real, and Mistral says its infrastructure was not breached du... The claim surfaced days after the Mini Shai‑Hulud campaign compromised more than 170 npm and PyPI packages, including Mistral AI SDK releases.
What should I do next in practice?
Security researchers say the alleged leak could stem from stolen developer credentials or simply be opportunistic fraud exploiting publicity around the attack.
The attack affected widely used developer libraries and tooling, including projects connected to:
TanStack
Mistral AI
UiPath
OpenSearch
Guardrails AI
Malicious versions of these packages contained credential‑stealing malware designed to collect secrets from developer machines, such as cloud credentials, GitHub tokens, and CI/CD environment data.
In the case of Mistral AI, attackers inserted malicious code into one of the official SDK releases distributed through package repositories.
What Happened With the Mistral AI SDK
Mistral confirmed that the incident involved compromised SDK package releases, not a breach of its core systems. According to the company’s security advisory:
Malicious versions of several npm and PyPI packages were briefly published.
The affected versions included packages such as @mistralai/mistralai (2.2.2–2.2.4) and the Python package mistralai (2.4.6).
The compromised releases were uploaded between May 11–12, 2026 and quickly removed once discovered.
The malicious Python package executed code automatically when imported. It downloaded a secondary payload named transformers.pyz from a remote server and launched it as a background process on Linux systems.
Did Attackers Breach Mistral AI’s Infrastructure?
Mistral’s investigation states that its internal infrastructure was not compromised. The company says forensic analysis traced the issue to a compromised developer device, not to a breach of internal production systems.
That distinction matters: a developer workstation compromise could allow attackers to publish malicious packages without gaining access to internal infrastructure or core repositories.
Why the Alleged Leak Is Still Unverified
Despite the forum claim, several factors prevent investigators from confirming the authenticity of the supposed data dump.
First, no sample files or repository metadata have been publicly released that could be checked against known Mistral codebases. Second, no third‑party security firm has verified the data. Finally, Mistral itself has not acknowledged any confirmed repository theft.
In practice, verifying a leak of this type would require evidence such as:
Valid Git commit history tied to private repositories
Matching internal repository structure
Cryptographic signatures or build artifacts
Confirmation from affected maintainers
None of these indicators have been presented publicly so far.
How This Fits Into TeamPCP’s Broader Campaign
The claim appears amid a wider wave of attacks targeting the open‑source software supply chain. Security researchers link TeamPCP to repeated compromises of popular development packages, often designed to steal credentials from developer environments and CI pipelines.
The Mini Shai‑Hulud campaign demonstrates how quickly these attacks can spread: hundreds of malicious package versions were published within hours across multiple ecosystems.
Within that context, the alleged Mistral repository sale could represent one of two possibilities:
A genuine attempt to monetize data obtained from compromised developer machines
An opportunistic claim meant to capitalize on the visibility of the supply‑chain incident
At the moment, public evidence is insufficient to determine which explanation is correct.
What Developers Should Take From the Incident
Regardless of the repository‑sale claim, the confirmed SDK compromise highlights the broader risks facing modern software supply chains. Attacks targeting package ecosystems can rapidly propagate malware to thousands of systems if developers install compromised versions before they are removed.
For organizations using affected ecosystems, common defensive steps include:
auditing installed package versions
rotating credentials that may have been exposed
monitoring CI/CD environments for unusual activity
The situation surrounding the alleged Mistral AI source code sale remains fluid. Until verifiable proof appears, security researchers treat the claim as unconfirmed speculation tied to a very real supply‑chain attack.
The attack affected widely used developer libraries and tooling, including projects connected to:
TanStack
Mistral AI
UiPath
OpenSearch
Guardrails AI
Malicious versions of these packages contained credential‑stealing malware designed to collect secrets from developer machines, such as cloud credentials, GitHub tokens, and CI/CD environment data.
In the case of Mistral AI, attackers inserted malicious code into one of the official SDK releases distributed through package repositories.
What Happened With the Mistral AI SDK
Mistral confirmed that the incident involved compromised SDK package releases, not a breach of its core systems. According to the company’s security advisory:
Malicious versions of several npm and PyPI packages were briefly published.
The affected versions included packages such as @mistralai/mistralai (2.2.2–2.2.4) and the Python package mistralai (2.4.6).
The compromised releases were uploaded between May 11–12, 2026 and quickly removed once discovered.
The malicious Python package executed code automatically when imported. It downloaded a secondary payload named transformers.pyz from a remote server and launched it as a background process on Linux systems.
Did Attackers Breach Mistral AI’s Infrastructure?
Mistral’s investigation states that its internal infrastructure was not compromised. The company says forensic analysis traced the issue to a compromised developer device, not to a breach of internal production systems.
That distinction matters: a developer workstation compromise could allow attackers to publish malicious packages without gaining access to internal infrastructure or core repositories.
Why the Alleged Leak Is Still Unverified
Despite the forum claim, several factors prevent investigators from confirming the authenticity of the supposed data dump.
First, no sample files or repository metadata have been publicly released that could be checked against known Mistral codebases. Second, no third‑party security firm has verified the data. Finally, Mistral itself has not acknowledged any confirmed repository theft.
In practice, verifying a leak of this type would require evidence such as:
Valid Git commit history tied to private repositories
Matching internal repository structure
Cryptographic signatures or build artifacts
Confirmation from affected maintainers
None of these indicators have been presented publicly so far.
How This Fits Into TeamPCP’s Broader Campaign
The claim appears amid a wider wave of attacks targeting the open‑source software supply chain. Security researchers link TeamPCP to repeated compromises of popular development packages, often designed to steal credentials from developer environments and CI pipelines.
The Mini Shai‑Hulud campaign demonstrates how quickly these attacks can spread: hundreds of malicious package versions were published within hours across multiple ecosystems.
Within that context, the alleged Mistral repository sale could represent one of two possibilities:
A genuine attempt to monetize data obtained from compromised developer machines
An opportunistic claim meant to capitalize on the visibility of the supply‑chain incident
At the moment, public evidence is insufficient to determine which explanation is correct.
What Developers Should Take From the Incident
Regardless of the repository‑sale claim, the confirmed SDK compromise highlights the broader risks facing modern software supply chains. Attacks targeting package ecosystems can rapidly propagate malware to thousands of systems if developers install compromised versions before they are removed.
For organizations using affected ecosystems, common defensive steps include:
auditing installed package versions
rotating credentials that may have been exposed
monitoring CI/CD environments for unusual activity
The situation surrounding the alleged Mistral AI source code sale remains fluid. Until verifiable proof appears, security researchers treat the claim as unconfirmed speculation tied to a very real supply‑chain attack.
