Which versions of web3tool are malicious?

The following PyPI versions of web3tool are flagged malicious: 6.6.1, 6.6.2, 6.6.3, 6.6.4, 6.6.5, 6.6.6. Treat any of these as compromised.

How do I remediate web3tool if I installed it?

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

If web3tool was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is web3tool part of a known attack campaign?

Yes — web3tool is associated with the 2026-02-old-ethrpc-keys 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 web3tool across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for web3tool (6 malicious versions).

Malicious package

web3toolPyPI

Advisory published Feb 19, 2026Updated Feb 20, 2026

web3tool is a confirmed malicious PyPI package (MAL-2026-950) that steals credentials and exfiltrates sensitive data (malicious versions 6.6.1, 6.6.2, 6.6.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in web3tool (PyPI)

MAL-2026-950

Immediate action

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

pip uninstall web3tool

What this malware does

The malicious code is in the ethrpc-keys package, which is a clone of legitimate eth-keys, but contains a modification that silently exfiltrates the user's private key. Other packages in the campaign are also clones of legitimate packages, but the only modification is in pulling (directly or traversally) the malicious dependency. At the end, all packages in the campaign exfiltrate the private key.

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

Campaign: 2026-02-old-ethrpc-keys

Reasons (based on the campaign):

clones-real-package
exfiltration-crypto
crypto-related
action-hidden-in-lib-usage
The malicious code is intentionally included in a dependency of the package

Malicious versions

6 flagged

6.6.16.6.26.6.36.6.46.6.56.6.6

Indicators of compromise (SHA-256)

50b63ced7e162150a14fbfb557df8683707b72b361caf1243a14468fd910a036

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for web3tool (6 malicious versions).
If you installed it — respond
web3tool 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 web3tool was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. web3tool on PyPI has been identified as a malicious package (versions 6.6.1, 6.6.2, 6.6.3, 6.6.4, 6.6.5, 6.6.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-02-old-ethrpc-keys

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database