Which versions of wbe3 are malicious?

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

How do I remediate wbe3 if I installed it?

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

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

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

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

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

Malicious package

wbe3PyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

wbe3 is a confirmed malicious PyPI package (MAL-2024-10194) 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 wbe3 (PyPI)

MAL-2024-10194

Immediate action

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

pip uninstall wbe3

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)

7e76b4cbb0442aff073ac3562fd2688c5ed9e8bc4a8d7fa444cb62e8e61844e6

28ae523032100c5b6436e11da1644e4aedd8843ee730f8c87af2f4edb226f669

3c87e22f7813d9db1c8561e8b3ebc83576f1e2b309f0f93bc16b7056644421a8

9c97f1dc5d3f5a02d7b15d81e79b2cb4666f53228c6a465a9938cf075e46b97f

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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