Which versions of solana-utils are malicious?

The following PyPI versions of solana-utils are flagged malicious: 0.1.1, 0.1.2. Treat any of these as compromised.

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

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

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

Yes — solana-utils is associated with the RLMA-2025-01998, 2025-02-transaction-utils, RLUA-2026-00769 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-utils 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-utils (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging solana-utils across your stack and pipelines.

Malicious package

solana-utilsPyPI

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

MAL-2025-2999

Immediate action

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

pip uninstall solana-utils

What this malware does

The only thing the package does is send out all the given data about a cryptocurrency transaction, including the private key, to a hardcoded webhook.

Feedback from PyPI Team: the package "transaction-utils" may also exploit a known pip behavior to overwrite files of an existing legitime package and replace it with malicious content.

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

Campaign: 2025-02-transaction-utils

Reasons (based on the campaign):

crypto-related
action-hidden-in-lib-usage
A Telegram webhook is used to send collected data.

Malicious versions

2 flagged

0.1.10.1.2

Indicators of compromise (SHA-256)

5a5d0fd5dc0fb3c56c738433b9b2c4e703824f7d0b32549cd93da3daaa4393ff

b77af7d0f8aa44942052740ef1f9445d4c9832bfe1b146f38bd19f030188a9d8

4fcf79d026074d2ebc0ce48f578a5078acafca383dbd727a0b2e9f5a723f2702

697ed06d1331251802aa126e1816bd4541293f27bf4df24435a2ec385ab4e568

3930a5f34409d6beb930af2d76f075ad37696fdd4c1fb820d8fe7fcf5ebf576f

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

Campaign

RLMA-2025-019982025-02-transaction-utilsRLUA-2026-00769

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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