Which versions of openaes are malicious?

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

How do I remediate openaes if I installed it?

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

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

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

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

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

Malicious package

openaesPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10062

Immediate action

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

pip uninstall openaes

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)

456c1a0a0e487d340d757e59576ba38f28ddab2a39adff8ca2f67d31fa04684d

e5c124283533da9300d2a24a7466f5cf05e762b75bd839d3662c1023c842e382

77c67addacf53a3b5389c6c57d36378ef57c031c90d902bc9e44a102d74885d2

832f04764c41182e41f494e76490e99b47bdacbf6ece1ebeda4f0ac23c5d0f0b

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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