Which versions of @mistralai/mistralai are malicious?

The following npm versions of @mistralai/mistralai are flagged malicious: 2.2.2, 2.2.3, 2.2.4. Treat any of these as compromised.

How do I remediate @mistralai/mistralai if I installed it?

@mistralai/mistralai is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @mistralai/mistralai — how do I know if it already compromised me?

If @mistralai/mistralai was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @mistralai/mistralai part of a known attack campaign?

Yes — @mistralai/mistralai is associated with the GHSA-3q49-cfcf-g5fm campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @mistralai/mistralai across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @mistralai/mistralai (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @mistralai/mistralai across your stack and pipelines.

Malicious package

@mistralai/mistralainpm

Malicious code in @mistralai/mistralai (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3432

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @mistralai/mistralai

What this malware does

The package @mistralai/mistralai was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This package was compromised as part of the "Mini Shai-Hulud is back" worm by the TeamPCP threat actor.

The package will steal credentials and then propogate it to every package it has access to. The package also attempts to remain persistent.

Malicious versions

3 flagged

2.2.22.2.32.2.4

Indicators of compromise (SHA-256)

dcf2132407f8778c7495e43c1e0891373066ccd550d4af3c2dfc8e19b8b84b56

0f23c44999cf920fc4d7fe1b3fa78d3e6e64155b1123d395c0df38844c8cfad2

5e1924464368f0c5816ee84e000cc47017f44045140feafbbc9e685d847ed5a5

23235945a2d68899f5fe2e6eafaefa0a98f2120697d41a40d26615e41aceb916

402f67b2439efd7a3fd22f94c22fe8d9ef3396cc2a9cc2cd9532f50c18a3a79b

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @mistralai/mistralai (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @mistralai/mistralai across your stack and pipelines.
If you installed it — respond
@mistralai/mistralai is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @mistralai/mistralai was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @mistralai/mistralai before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @mistralai/mistralai on npm has been identified as a malicious package (versions 2.2.2, 2.2.3, 2.2.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-3q49-cfcf-g5fm

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @mistralai/mistralai-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring