Which versions of web3-py-checksum are malicious?

The following PyPI versions of web3-py-checksum are flagged malicious: 1.0, 1.1. Treat any of these as compromised.

How do I remediate web3-py-checksum if I installed it?

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

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

Yes — web3-py-checksum is associated with the 2026-05-old-web3-py-checksum, RLMA-2026-02118 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 web3-py-checksum across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for web3-py-checksum (2 malicious versions).

Malicious package

web3-py-checksumPyPI

Advisory published May 10, 2026Updated Jul 9, 2026

web3-py-checksum is a confirmed malicious PyPI package (MAL-2026-3411) that steals credentials and exfiltrates sensitive data (malicious versions 1.0, 1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in web3-py-checksum (PyPI)

MAL-2026-3411

Immediate action

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

pip uninstall web3-py-checksum

What this malware does

The code silently exfiltrates the private key of a crypto account.

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

Campaign: 2026-05-old-web3-py-checksum

Reasons (based on the campaign):

crypto-related
exfiltration-crypto

Malicious versions

2 flagged

1.01.1

Indicators of compromise (SHA-256)

4b2052172f5c854b2e91f6bdc9336a97469cd161372621a1880d9cd1e3ad426a

8e190704ac159c1e6be0cace465986fdb1f2453d84528f83f35b32c515bbde1c

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for web3-py-checksum (2 malicious versions).
If you installed it — respond
web3-py-checksum 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 web3-py-checksum 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. web3-py-checksum on PyPI has been identified as a malicious package (versions 1.0, 1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-05-old-web3-py-checksumRLMA-2026-02118

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter
ReversingLabs · finder

Detect & block this

O3 blocks web3-py-checksum-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