Which versions of openwae are malicious?

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

How do I remediate openwae if I installed it?

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

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

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

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

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

Malicious package

openwaePyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10086

Immediate action

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

pip uninstall openwae

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)

b29da0f0847f5b3a896d768357c9886329ed7cd4c59b7a404dc05d1a0bd7a40f

979d00f028f24fa0e881b7b30110da16cebdd4baaea715833cdef258caecfe77

264db26b8ff2f7f028376af04ab699a9af68748247df9f8fd7aee3a31bf02866

66ad1f0ceb2b30058cdaa6c4343fa4477cd85e67d8ae889b55f09041eeaabeff

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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