Which versions of web3node are malicious?

The following PyPI versions of web3node 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 web3node if I installed it?

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

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

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

Malicious package

web3nodePyPI

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

MAL-2025-3016

Immediate action

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

pip uninstall web3node

What this malware does

web3socket: In the class there is a hidden code that loads a binary Python code from a remote location impersonating PyPI Github account web3node: The package is used to download and run remote code by other packages. Files darwin.py, gnu.py and win32.py contain code that adds executing remote code to the crontab as well as an attempt to escalate privileges. w3socket: It uses web3node to start remote code in config.py

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

Campaign: 2025-02-web3socket

Reasons (based on the campaign):

dependency-confusion
impersonation
Downloads and executes a remote malicious script.

Malicious versions

4 flagged

0.1.00.1.10.1.20.1.3

Indicators of compromise (SHA-256)

9f7d028a6b3b2858230864bbc355eda0a452dfb688056fb4fae84fd0b15404f8

3f540afd8045a0249c52c523780828280acb6752ee85c16e648f6ae5e5f65f64

9f226e2391e0717c113d67f398aae7c36705ffbef3310caebd76a1b8b11f0811

dd079877a67f6fe8bd69db0f5bc6d0d9a7882b29726432cf7ae783d3006a2a3d

e6f0cbb0f7b8f8eee903940193477372e84b9a63574992f1e300f96d3b659039

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 web3node (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging web3node across your stack and pipelines.
If you installed it — respond
web3node 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 web3node 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 web3node 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. web3node 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-020152025-02-web3socketRLUA-2026-00919

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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