Which versions of solana-token are malicious?

The following PyPI versions of solana-token are flagged malicious: 0.0.1, 0.0.2, 1.0.1, 1.0.2. Treat any of these as compromised.

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

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

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

Yes — solana-token is associated with the RLMA-2024-09288, RLUA-2025-02598, 2025-05-solana-token, RLUA-2025-06592, RLUA-2026-00768 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 solana-token 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 solana-token (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging solana-token across your stack and pipelines.

Malicious package

solana-tokenPyPI

Malicious code in solana-token (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-10163

Immediate action

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

pip uninstall solana-token

What this malware does

Code exfiltrates the current python code and/or IPythonshell history

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

Campaign: 2025-05-solana-token

Reasons (based on the campaign):

crypto-related
impersonation
action-hidden-in-lib-usage
exfiltration-crypto

Malicious versions

4 flagged

0.0.10.0.21.0.11.0.2

Indicators of compromise (SHA-256)

3af9e34e93808039c48ece4be57e9f22210574c2aab263c631d1183d1a133ed7

e4d185e5fe7c22ac5e80ff0c3d3cc2598f02497cfbd299cba85d686b824efe0a

fe70d9b7a3d2ff8f1bd664f171185322f1c2573e682a68f25101505db792ee5c

7a052cb86f0a3ef5266420bcfed9256955a31ea75bfe4197c42d3a2740621ab4

780ea5fb9284193b8321f0e53ac1a9945ea3098cb7b97db3ba76a4908708c357

a6f4b3c1f8e11b9b0ca772e26459e9f294555125735d4c42e1270df753f8fcab

c181c2f22b899e2a1e80131593e4bff523002b6b987ffd2097aa876471619019

80ee279a1651492580e69f69d96a54552311ba3add85c3cbdd97f501df4b814a

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 solana-token (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging solana-token across your stack and pipelines.
If you installed it — respond
solana-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 solana-token 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 solana-token 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. solana-token on PyPI has been identified as a malicious package (versions 0.0.1, 0.0.2, 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-09288RLUA-2025-025982025-05-solana-tokenRLUA-2025-06592RLUA-2026-00768

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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