Which versions of web3yrpcs are malicious?

The following PyPI versions of web3yrpcs are flagged malicious: 1.1.2. Treat any of these as compromised.

How do I remediate web3yrpcs if I installed it?

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

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

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

Malicious package

web3yrpcsPyPI

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

MAL-2025-4272

Immediate action

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

pip uninstall web3yrpcs

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

1 flagged

1.1.2

Indicators of compromise (SHA-256)

02407a1ef9536438cbb08658bb0328e4ca6657a6214ebd329bc8b56b57c058c1

defde073e7bd3ba063a00577964c26c6256d20a9221cc4de5f675598618e5062

171ec4f4bbfb34688348ecdda292249487574c8fb28caf8467c0bbafb1563cb7

6cae6c04abcfa97bd481e2ea2bb7fab7613522da692eab369c4af589addbf971

b6f73f2a0ef14631157a06327e68782be871d8e66e3b2bd4ca0262dc50b6c557

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

Campaign

RLMA-2025-026302025-04-alchemyrpcsRLUA-2026-00923

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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