Which versions of werb3 are malicious?

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

How do I remediate werb3 if I installed it?

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

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

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

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

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

Malicious package

werb3PyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10214

Immediate action

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

pip uninstall werb3

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)

0898bee2de13a4d37199158901144ee9a0183fa2953ad0e702a7c593fed7aac9

e664a4a843cd8f5e03262c818f4a0877d5c833fa3f313d643068e8e235f407b0

50b23b39e8aa23e8b125c5a72c2d6279ba2d6056992a2d1fdf2f90997eba5974

3bc9806936b2776f57fcc969e96b5867c3ddc1f1ae6d35d34e68f732a55df5be

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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