AI Risk Wire

Cases › security breach › LR-2026-0533

Mistral AI source code stolen in data breach and offered for sale

Preliminary Why: Publisher not yet named · subject to change

Status: fix reported

Severity moderate
Reported 12 May 2026

No source states: loss or records, developer and model, agent tool, could do, deployer, industry.

Severity moderate: Test: data of others touched with a bounded scope stated. Fact: the attackers accessed certain non-core code repositories only, per Mistral's account as reported.

A supply-chain attack on the open-source TanStack ecosystem, attributed to the group TeamPCP, reached Mistral AI's development environment. Attackers chained GitHub Actions weaknesses to publish malicious packages through TanStack's trusted pipeline, and the malware spread to Mistral's own SDK packages. Mistral said attackers temporarily compromised one codebase management system on May 12, 2026, and that it neutralized the attack and launched a forensic investigation. The group then offered about 450 repositories for sale at $25,000, claiming they contain internal AI source code and training material. These claims remain unverified, and Mistral's advisories do not confirm the advertised scope.

What happened

1 · How it was caughtMistral said it quickly neutralized the attack, secured its infrastructure, and launched a forensic investigation with relevant authorities.

What was done

Fix reported

“Attack neutralised, infrastructure secured, forensic investigation launched with relevant authorities”

Risks

AI used to run a cyber attack
Primary96 incidents
Rising: 24 vs 4.0 a week
AI system attacked or breached
Also23 incidents

Sorted by rule from the case's fields; not yet read from the sources.

Controls

Not yet read for controls. Controls that mitigate the primary risk:

Model

Safety training and refusal · Cyber and weapons safeguards · Abuse monitoring and account enforcement · Staged or restricted release · Dangerous-capability testing before release · Outside red-teaming · Content safety classifiers · Safeguards kept on in testing · Reasoning monitoring

Infrastructure / target

Known flaws patched · Multi-factor sign-in and password policy · Network segmentation · Intrusion and endpoint detection · Backups and recovery · Phishing and fraud filters

Evidence

No source states: what the AI was doing, what went wrong, what it reached or did, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case, the cause, what set it off, what was done.

Show the full account: 2 items from the primary sources

What happened, in order

  1. May 11, 2026, between 19:20 and 19:26 UTC TeamPCP published 84 malicious npm package artifacts across 42 packages in the TanStack namespace.
  2. May 12, 2026 Attackers temporarily compromised one of Mistral AI's codebase management systems.
Show every field, with its source and grade

What happened

When it happened
2026-05-12
C one secondary source states it
Who was responsible
an outside party
C one secondary source states it
What was done
Attack neutralised, infrastructure secured, forensic investigation launched with relevant authorities
C one secondary source states it
What went wrong
security breach
D inferred by us from the described behaviour, reason shown

Impact

Severity
moderate
D inferred by us from the described behaviour, reason shown
Why this severity
Test: data of others touched with a bounded scope stated. Fact: the attackers accessed certain non-core code repositories only, per Mistral's account as reported.
D inferred by us from the described behaviour, reason shown

LR-2026-0533 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON