Which versions of solana-coin are malicious?

The following PyPI versions of solana-coin are flagged malicious: 0.0.1. Treat any of these as compromised.

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

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

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

Yes — solana-coin is associated with the RLMA-2025-03033, 2025-05-solana-token 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-coin 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-coin (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging solana-coin across your stack and pipelines.

Malicious package

solana-coinPyPI

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

MAL-2025-5136

Immediate action

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

pip uninstall solana-coin

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

1 flagged

0.0.1

Indicators of compromise (SHA-256)

972e53d1c285f0c78986df1d0c65eb79da7c5eab31e4fb5f2f774935f4091762

0fd8df1f6450c73539af68b8f13f4878dbfc4abbf2b98498523b5771422c7388

fa4c17031f4a667cddae42a648aa66edf30f498296c451a2c0637082772dbcef

07bf6241a15e072bf32007609af4c08cb5e44cfff672beaff35eb1161272336e

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

Campaign

RLMA-2025-030332025-05-solana-token

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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