Which versions of openzsea are malicious?

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

How do I remediate openzsea if I installed it?

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

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

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

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

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

Malicious package

openzseaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10095

Immediate action

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

pip uninstall openzsea

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)

148ef3f9e08365732efd73e8ce7a63bf696d28aef18d03fb8c7e70ba652c0eba

3d59271d63d582ba9322877a4a9ee20baf7b4bc150397c39d5fc0294e0d8d32b

17ca0b734a90f2a5de10d45a3271f2d49a0772fc64f1b9349e9a1947df29b5dc

c0bfeeda6adc4ddd86b36df85d548c2f4738569d87cae8bd79c60aed63b658cd

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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