Which versions of openwea are malicious?

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

How do I remediate openwea if I installed it?

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

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

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

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

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

Malicious package

openweaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10087

Immediate action

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

pip uninstall openwea

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)

b57b02f35b2ff948dac8cf8e6daf37d0d8f16d69d28742a832d7dab86dfdbb05

2605adca36a8b9b15e891c1730bff1247eacbe72f0e4c079de051e131d2d1663

a525305442100b68d8fd1fe5258514f54b363e0fdd927ae12fe166451130e0a0

731e031a237449def5f533147ebec53b8c4333f93374dfecd16c20fcfb9935a7

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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