Which versions of alchemyrpcs are malicious?

The following PyPI versions of alchemyrpcs are flagged malicious: 1.1.7, 1.1.8. Treat any of these as compromised.

How do I remediate alchemyrpcs if I installed it?

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

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

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

Malicious package

alchemyrpcsPyPI

Malicious code in alchemyrpcs (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-4205

Immediate action

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

pip uninstall alchemyrpcs

What this malware does

Package contains just a function to send out data. It (or a package sharing the same IoCs) is used in a malicious GitHub project to exfiltrate crypto currency private keys, e.g. https://github.com/taikoyaki/MegaEth-Auto-Bot/blob/772b4591daaa0b200d1bd1fd3be3d48b8433f084/cap/cap.py#L49

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

Campaign: 2025-04-alchemyrpcs

Reasons (based on the campaign):

crypto-related
The malicious code is intentionally included in a dependency of the package
exfiltration-crypto

Malicious versions

2 flagged

1.1.71.1.8

Indicators of compromise (SHA-256)

aebefbf3548e23a3f7e0a9653ea5b537a55f0f6f420aa1c46b5147ad40e77ad7

d7ec9147de539e312f3d4e09b0971460b24145438a4de32d20786048aa37d84e

c3de5cb8ee8e308aa3b7dbfcb71e5c3d5becf9c41b1bdfee75a00b4a29c3663a

ba242d3294e0f4adb923c06b0070970a8d83ba9e113f2c7ba3dbb25de68a24e1

9fd4fb2848d2c7dad364588cda328de035d3a4d3543f13cc753bcaa59c9f435c

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

Campaign

RLMA-2025-025552025-04-alchemyrpcsRLUA-2026-00053

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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