Which versions of raydium are malicious?

The following PyPI versions of raydium are flagged malicious: 2.1.1, 2.1.4, 2.1.5, 2.1.6. Treat any of these as compromised.

How do I remediate raydium if I installed it?

raydium 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 raydium — how do I know if it already compromised me?

If raydium was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is raydium part of a known attack campaign?

Yes — raydium is associated with the spl-types-rentry-2024-07 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 raydium across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for raydium (4 malicious versions).

Malicious package

raydiumPyPI

Advisory published Jul 3, 2024Updated Dec 31, 2025

raydium is a confirmed malicious PyPI package (MAL-2024-12336) that steals credentials and exfiltrates sensitive data (malicious versions 2.1.1, 2.1.4, 2.1.5…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in raydium (PyPI)

MAL-2024-12336

Immediate action

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

pip uninstall raydium

What this malware does

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: spl-types-rentry-2024-07

Reasons (based on the campaign):

infostealer
crypto-related

Malicious versions

4 flagged

2.1.12.1.42.1.52.1.6

Indicators of compromise (SHA-256)

88d718fa542749a22f4a60376aa359d1d2f7b60b372d278784a8ce8075245c79

236ebe472d3c676e9d99d6370d989ade43f7acdec0a2076c3dedbc9682b8f3a2

aebec87d8b55ed2a61e6cc43156fb26ac4dc8edfb76c19b00ad0f30c8a240c3c

41d87efc2abd66c43262d53c189918e04d623280b05821ed4f2c38b3bccab5ec

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for raydium (4 malicious versions).
If you installed it — respond
raydium 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 raydium was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. raydium on PyPI has been identified as a malicious package (versions 2.1.1, 2.1.4, 2.1.5, 2.1.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

spl-types-rentry-2024-07

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks raydium-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

Explore

All malware advisories How O3 detects malware Vulnerability database