Which versions of openza are malicious?

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

How do I remediate openza if I installed it?

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

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

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

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

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

Malicious package

openzaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10093

Immediate action

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

pip uninstall openza

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)

d3ea98b48318bda8bff0f4299a439ff845ae80aa6195062e980bc21a976bbf37

36beee7320e141fea6286e6ca2b799753561283e54755eeaf6652a35fe36ff1a

fbaf59e19187d3a389d16ea0c20582da8f14f37c0df06e004fa36024ae6ab9bf

4f67c5544c9c465e773236da4b7681898203f8c497b347d2f6a16add3ae31289

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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