Which versions of openes are malicious?

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

How do I remediate openes if I installed it?

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

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

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

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

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

Malicious package

openesPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10066

Immediate action

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

pip uninstall openes

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)

e42df9915e169f378408e33688d3d9fa7c7501684e8c55f7eeebd7b55ae05711

6d438f45add4f2a973ffee4bde020c51740544d95da8897f66617890d13c7370

1a0378066f6b09d44f6e8d504ba7adbc402afd600d8f6904c5cc8c9ed54e078a

4ccbe307e1f41f2501351e283fc8cd04f036fac45af931377207e3c011869032

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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