Which versions of openesa are malicious?

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

How do I remediate openesa if I installed it?

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

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

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

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

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

Malicious package

openesaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10067

Immediate action

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

pip uninstall openesa

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)

b1206af946b761364ec433e7b778710f7421d2766f75fc51a7e38b763ef9554d

7ba52c23906b3a6a9f77e28ce82f99d5f441d645a6a3af60d4f973a3ce7cba2d

70a3328185d9986ea8c57cbce23a26d53c2fb2579496b24f6aca1710cdb860ae

8f5fc2d78c4bfe86650f7be69ecdb12dc63f4a121ea190dce5e2c882133334bb

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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