Which versions of oopenwea are malicious?

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

How do I remediate oopenwea if I installed it?

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

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

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

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

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

Malicious package

oopenweaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10059

Immediate action

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

pip uninstall oopenwea

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)

47ab81c4d3768f420f3c190f0ae2ea68b5345aff5dd04b33b69d88fa25fffaed

c58a8a07269e238c4d3be631620095ec1da22db4d00628c9206584f61f1a460a

d15a9c585b66c78ca0b38be3e8b19caa02d4122ed578beb44806c689ddea8235

22bf9d999129a2e5de8158477cccdce30b974402d6b723150f8385b6f5826458

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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