Which versions of openesaa are malicious?

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

How do I remediate openesaa if I installed it?

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

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

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

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

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

Malicious package

openesaaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10068

Immediate action

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

pip uninstall openesaa

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)

59c621a7e1364366b3df572d1ff7591a759d45377eeadf6c39c90b017d1522ce

3533c9abf755346802f3c1a2a92b970f855fe695aaf72eab90aedb559afe2bab

9046579c11ebb423eeb460c67c508dc4aab15ddb9a81ff6f9ca6966980dd888d

2716bf18d8e44c9350152ca820aac3e22e68a7e27c0bb4bdbe200da2b2af2be6

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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