Which versions of walletrpcs are malicious?

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

How do I remediate walletrpcs if I installed it?

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

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

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

Malicious package

walletrpcsPyPI

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

MAL-2025-4259

Immediate action

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

pip uninstall walletrpcs

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

0.1.10.1.2

Indicators of compromise (SHA-256)

1c335312078d6c83b7a66f9d972dffae56f3690b531751c32d8b3173df271adb

197fe5241eed4cfc5cdf59c2146f280ef01e5762e7846f7fe25d6867e5d8bd70

4b93b9b49f17c924bbca7ba78750257a7be53f8d48ad200a16dc5eb4e369a734

9fa9e6f1425c148d5772e2946735741bc4bafb6baa8796d80698b35c5884451e

10b627cd3fb220af14662cc9766c20630569589a127c8b5d9332459cf297b1ea

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 walletrpcs (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging walletrpcs across your stack and pipelines.
If you installed it — respond
walletrpcs 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 walletrpcs 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 walletrpcs 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. walletrpcs 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-026172025-04-alchemyrpcsRLUA-2026-00903

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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