Which versions of openxsea are malicious?

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

How do I remediate openxsea if I installed it?

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

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

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

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

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

Malicious package

openxseaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10092

Immediate action

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

pip uninstall openxsea

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)

bf0740d393defa67df76d3e93958d57d95d61d822a572fd7e1031535ae353d38

a36a5a44ec7d1745dc3dc0854c61a67b00c87dd83a7b8d345aeb7b374610e768

f11108218119ec2513a1ed4ddee206e937caf8e08151d5702c1d847d6ebd1107

57ba1fb9aaee1e82d18a7fcad3cb5628e99191e9aa065a01a882b1bce1328db7

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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