Which versions of etherweb3 are malicious?

The following PyPI versions of etherweb3 are flagged malicious: 0.3.9, 0.3.10, 0.3.11, 0.4.2. Treat any of these as compromised.

How do I remediate etherweb3 if I installed it?

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

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

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

Malicious package

etherweb3PyPI

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

MAL-2025-47764

Immediate action

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

pip uninstall etherweb3

What this malware does

Malicious clone of a legitimate "web3" package. During importing, a code aiming to exfiltrate private keys is executed

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

Campaign: 2025-08-etherweb3

Reasons (based on the campaign):

exfiltration-crypto
crypto-related
clones-real-package

Malicious versions

4 flagged

0.3.90.3.100.3.110.4.2

Indicators of compromise (SHA-256)

038e484cdc4348c49a74fb5f336b79ed6ea39f0662d0a5cabf6b31bee8557955

9310821b956843395eecc0090680966e41571541b9ceb6322addf252b2823c38

500af99cbff4bad856e50637e3046662824ccdde4cbf8f35cfe5d6bb2c880ce8

573ae3dd4f93be0d622e9628c6af89d9a1749711e5612dd06b8f97db05965c00

e7fb71888483b39ae2a745f686f57be13618d33436cd992b2782361d324ec240

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

Campaign

RLMA-2025-047652025-08-etherweb3RLUA-2026-00299

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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