Which versions of spl-token are malicious?

The following PyPI versions of spl-token are flagged malicious: 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.5. Treat any of these as compromised.

How do I remediate spl-token if I installed it?

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

If spl-token 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 spl-token part of a known attack campaign?

Yes — spl-token is associated with the RLMA-2024-09303 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 spl-token across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for spl-token (5 malicious versions).

Malicious package

spl-tokenPyPI

spl-token is a confirmed malicious PyPI package (MAL-2024-10167) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.1, 0.1.2, 0.1.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in spl-token (PyPI)

MAL-2024-10167

Immediate action

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

pip uninstall spl-token

Malicious versions

5 flagged

0.1.10.1.20.1.30.1.40.1.5

Indicators of compromise (SHA-256)

671b9dba0016e6300b153b64cce02d232e05bfdc84624bd265e40710f2455cfb

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for spl-token (5 malicious versions).
If you installed it — respond
spl-token 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 spl-token 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. spl-token on PyPI has been identified as a malicious package (versions 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-09303

Credits

ReversingLabs · finder

Detect & block this

O3 blocks spl-token-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