Which versions of w3b-py are malicious?

The following PyPI versions of w3b-py are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate w3b-py if I installed it?

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

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

Yes — w3b-py is associated with the RLMA-2024-09486, funcaptcha-ru 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 w3b-py 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 w3b-py (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging w3b-py across your stack and pipelines.

Malicious package

w3b-pyPyPI

Malicious code in w3b-py (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-10188

Immediate action

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

pip uninstall w3b-py

What this malware does

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

Campaign: funcaptcha-ru

Reasons (based on the campaign):

infostealer

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

d4cfbf7eb80db371d3905883b8fcdd94141ac9121d09ed29d0ba24dd1034aa9d

0d41a8c9557e87f72bc0be1cabeb4445220beafc6494eb4eba96d446dcddb315

bd8f518df8aff7869e1bbf6cfd02e1f9c6b58eb38525322d90e06a72b4df9dca

ad01fca6ff3d0eb27413c34190852295af3ef24a501d6fdf200bc446b2b19de0

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

Campaign

RLMA-2024-09486funcaptcha-ru

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks w3b-py-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