Which versions of solana-trade are malicious?

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

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

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

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

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

Malicious package

solana-tradePyPI

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

MAL-2025-5139

Immediate action

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

pip uninstall solana-trade

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

1.0.0

Indicators of compromise (SHA-256)

87ac3ca32f3d297d801fcd7729ff4ff74a989a53f0211ab867d038a42f02c352

d3b5a0101b90e0ca047f69d2207adc90f7ec514f8d95436c5dc27f4398ad468d

e84e568bb86db442dd7d2e19e6fa1805ea10085d9926220d986941d87ca99259

47aa57ff1538588d75ceed5bf09b123968a882c847167a28464d252eed9c2f42

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

Campaign

RLMA-2025-030362025-05-solana-token

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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