Which versions of openzea are malicious?

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

How do I remediate openzea if I installed it?

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

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

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

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

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

Malicious package

openzeaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10094

Immediate action

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

pip uninstall openzea

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)

9b57a01b9f94a5fd55e62eb506049ab362f13fb6c224e092897f1b7bfca0192c

198cc9aef33ba829d7eef12deaa13d4bf761b3cab5f79258fc49cc418e6f8e35

55a0dc7e2a2ad07f7da0739dd3be2f54e109446152f4a098f265f81738a0aa10

2cf87b3db91b7034fe0fded38f4bbf95ca79a1d7f9467da780da89873abbe10b

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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