Which versions of solana-transaction are malicious?

The following PyPI versions of solana-transaction are flagged malicious: 0.1.0, 1.0.0, 1.0.1, 1.0.2, 1.0.4, 1.0.5, 1.0.6, 1.0.7. Treat any of these as compromised.

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

Remove solana-transaction from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed solana-transaction — how do I know if it already compromised me?

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

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

Search your lockfiles and build artifacts for solana-transaction (8 malicious versions).

Malicious package

solana-transactionPyPI

solana-transaction is a confirmed malicious PyPI package (MAL-2024-10164) that executes malicious code on install (malicious versions 0.1.0, 1.0.0, 1.0.1…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in solana-transaction (PyPI)

MAL-2024-10164

Immediate action

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

pip uninstall solana-transaction

Malicious versions

8 flagged

0.1.01.0.01.0.11.0.21.0.41.0.51.0.61.0.7

Indicators of compromise (SHA-256)

54619e9f521a0e1a9eadb354f676c403a85acca23cb9263b2ddde2af8828009d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for solana-transaction (8 malicious versions).
If you installed it — respond
Remove solana-transaction from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If solana-transaction 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. solana-transaction on PyPI has been identified as a malicious package (versions 0.1.0, 1.0.0, 1.0.1, 1.0.2, 1.0.4, 1.0.5, 1.0.6, 1.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-09289

Credits

ReversingLabs · finder

Detect & block this

O3 blocks solana-transaction-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database