Which versions of web3evm are malicious?

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

How do I remediate web3evm if I installed it?

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

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

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

Malicious package

web3evmPyPI

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

MAL-2025-5142

Immediate action

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

pip uninstall web3evm

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

4 flagged

0.1.00.1.10.1.20.1.3

Indicators of compromise (SHA-256)

c5b7092971e2231d110944e8ef03efa2aa8c0c3e5c1c2a1268ee64096348958f

73cdff85b939d243524dad0af0b064dd1e694d3491b1b3b2044f94a20597da5d

6c2f7724a72031eda7b5c33755802a67784979e2a9459d83698b0637be68630b

7ddc21819c79e94852afae6b5d2859f71c8cc0d7d4c44eebaff1e6a05cba2a85

5392e10172907060037a42aa93ba5cb6d0c103961ebfd434fec7c3c354e715f0

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

Campaign

RLMA-2025-030392025-04-alchemyrpcsRLUA-2026-00917

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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