Which versions of web3socket are malicious?

The following PyPI versions of web3socket are flagged malicious: 0.0.1, 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4. Treat any of these as compromised.

How do I remediate web3socket if I installed it?

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

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

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

Malicious package

web3socketPyPI

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

MAL-2025-3017

Immediate action

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

pip uninstall web3socket

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

6 flagged

0.0.10.1.00.1.10.1.20.1.30.1.4

Indicators of compromise (SHA-256)

ad554082bcf7b705dcf5a8964df8ad4312cf42cc59df0d5e7228148b4dd06bee

28243a2c1417e0506af406800506001b7248889f46fd522d200fd5fb7db8eef7

7dc7eadb2f62e32882fffd4423ba15f5dda9f6f157a2c6eedbb7d040602237ed

f3bfa63b36d2cf8afc90fac85d16582366e2f50c1ae3245650e5ef46c626b202

d3442398eeefe900e1b90adf57287e07fc5ef71555f6d4722bf08609f118cb2a

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

Campaign

RLMA-2025-020162025-02-web3socketRLUA-2026-00920

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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