Summary
Broken dropper in @mistralai/mistralai, @mistralai/mistralai-azure, @mistralai/mistralai-gcp
Mistral npm @mistralai/mistralai, @mistralai/mistralai-azure, @mistralai/mistralai-gcp were compromised by a supply chain attack related to the TanStack security incident. An automated worm associated with the attack led to compromised npm package versions being published.
Current investigation indicates that an affected developer device was involved. We have no indication that Mistral infrastructure was compromised. The compromised versions were removed from npm. They were available only between May 11 at 22:45 UTC and May 12 at 01:53 UTC. Previous and later versions are not affected by this advisory.
Check whether you are affected
You are affected if one of the package versions above was installed in any environment during the exposure window or is present in a lockfile, build artifact, container image, package cache, or deployment image.
| Package | Affected versions |
|---|---|
@mistralai/mistralai |
2.2.2, 2.2.3, 2.2.4 |
@mistralai/mistralai-azure |
1.7.1, 1.7.2, 1.7.3 |
@mistralai/mistralai-gcp |
1.7.1, 1.7.2, 1.7.3 |
Check installed versions:
npm ls @mistralai/mistralai @mistralai/mistralai-azure @mistralai/mistralai-gcp
grep -n -A 4 -B 2 -E '@mistralai/(mistralai|mistralai-azure|mistralai-gcp)|2\.2\.[2-4]|1\.7\.[1-3]' \
package-lock.json pnpm-lock.yaml yarn.lock 2>/dev/null
Look for any of the following files
router_init.js(embedded in all @tanstack packages):ab4fcadaec49c03278063dd269ea5eef82d24f2124a8e15d7b90f2fa8601266ctanstack_runner.js(from git commit):2ec78d556d696e208927cc503d48e4b5eb56b31abc2870c2ed2e98d6be27fc96@tanstack/setuppackage.json:7c12d8614c624c70d6dd6fc2ee289332474abaa38f70ebe2cdef064923ca3a9b
You may also run this (read-only) script that will automatically flag known malicious files.
You are not affected by this advisory if you did not install the affected package versions and they are not present in your lockfiles, build caches, deployment artifacts, or package mirrors.
If the command finds an affected version, continue with the remediation steps below. If you use private package mirrors, caches, or container base images, check those copies too.
Remediate affected systems
- Stop using the affected package version immediately.
- Clean systems where one of this package has been installed.
Impact
The dropper is broken, it has no impact.
setup.mjsreferencestanstack_runner.jsbut the payload file is namedrouter_init.jsexecFileSyncthrowsENOENTand the tmpdir is wiped before payload runs. Bun gets downloaded to a tmpdir but no payload execution.
We still recommend removing the packages, see below for remediation.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-JGG6-4RPR-WFH7? GHSA-JGG6-4RPR-WFH7 is a low-severity security vulnerability in @mistralai/mistralai (npm), affecting versions = 2.2.2. No fixed version is listed yet.
- Which packages are affected by GHSA-JGG6-4RPR-WFH7?
@mistralai/mistralai(npm) (versions = 2.2.2)@mistralai/mistralai-azure(npm) (versions = 1.7.1)@mistralai/mistralai-gcp(npm) (versions = 1.7.1)
- Is there a fix for GHSA-JGG6-4RPR-WFH7? No fixed version is listed for GHSA-JGG6-4RPR-WFH7 yet. Monitor the advisory for updates and apply mitigations in the interim.
- Is GHSA-JGG6-4RPR-WFH7 exploitable, and should I be worried? Whether GHSA-JGG6-4RPR-WFH7 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-JGG6-4RPR-WFH7 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.