Which versions of openseax are malicious?

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

How do I remediate openseax if I installed it?

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

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

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

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

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

Malicious package

openseaxPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10079

Immediate action

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

pip uninstall openseax

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)

0a1e346758bfa5a44ffd5c451d710c10228741aa5fd1e6eaea973512ebc44c58

055ee5cce961485325990de0634fb329cc1d548e21b134568ec728e7ae25a920

ec03d53d7d2432e27da1d77449f8fb3988d72c9ad4c7d9950dffa1fa0830e3c5

69f140f2cf5d85a524f58b5bdbdc302ab5c4e937d11f0fd7bddb2e95eb765168

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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