Which versions of w3b are malicious?

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

How do I remediate w3b if I installed it?

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

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

Yes — w3b is associated with the RLMA-2024-09485, 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 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for w3b (version 1.0.0).

Part of a larger attack: funcaptcha-ru published 161 malicious packages. See the full campaign →

Malicious package

w3bPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

w3b is a confirmed malicious PyPI package (MAL-2024-10187) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in w3b (PyPI)

MAL-2024-10187

Immediate action

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

pip uninstall w3b

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)

b463a3b9151729e18d0e6423ee200b40f3f27f709e555c90cb8031cd0f42db1a

3a52551666a86c46bbddac5d466c30ec625a9c4339e7b4f58a99cd6e2da06b7f

248f2c4080bb73ac165e55444ef2fe0eadfd0df17bda6fdf5ad9e6fb2ca68793

e5bc509155fcd45e6e0da0b9a75ba5c9120673645f8cbd98d2d4204a7ebe0897

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for w3b (version 1.0.0).
If you installed it — respond
w3b 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 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. w3b 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-09485funcaptcha-ru

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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