Which versions of web3-request are malicious?

The following PyPI versions of web3-request are flagged malicious: 1.7.53, 1.8.54. Treat any of these as compromised.

How do I remediate web3-request if I installed it?

Remove web3-request from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed web3-request — how do I know if it already compromised me?

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

Yes — web3-request is associated with the RLMA-2025-02623 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-request across my projects, lockfiles, and CI pipelines?

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

Malicious package

web3-requestPyPI

web3-request is a confirmed malicious PyPI package (MAL-2025-4265) that executes malicious code on install (malicious versions 1.7.53, 1.8.54). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in web3-request (PyPI)

MAL-2025-4265

Immediate action

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

pip uninstall web3-request

Malicious versions

2 flagged

1.7.531.8.54

Indicators of compromise (SHA-256)

3d7e8c9c1c8798901f51bdf3e889841d8dbb8076729a63edbc9f4e4b2671b7e2

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for web3-request (2 malicious versions).
If you installed it — respond
Remove web3-request from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If web3-request 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-request on PyPI has been identified as a malicious package (versions 1.7.53, 1.8.54 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-02623

Credits

ReversingLabs · finder

Detect & block this

O3 blocks web3-request-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database