Which versions of wweb3 are malicious?

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

How do I remediate wweb3 if I installed it?

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

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

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

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

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

Malicious package

wweb3PyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10218

Immediate action

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

pip uninstall wweb3

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)

917be389cd3f67dbc976188c2c0327d5522f65081e3895de04b98b10dbc567a7

f13c0dac329bc3baaec6f68334419e7110a9927592ff059a1baddac71ec73714

00f157ccda5990a3956f6f8b244e220f7935b7a59081eab378d8abe84dd93215

8e22199b705a565671bc1803bb5ef5f01a1e488f4ccc2bd39a59ff35634f0127

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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