Which versions of openseea are malicious?

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

How do I remediate openseea if I installed it?

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

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

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

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

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

Malicious package

openseeaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10082

Immediate action

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

pip uninstall openseea

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)

8f564753abfef4c1dc2a4ef2dba4fec97d76bd488a51d2f53ff55c3c16661404

d04ca794482f4ed05a610115c1adbeced142b65e3ce326ef9e0c3499ca33c18f

f00ed3c536ba4055ac9f428a4aa2ae24c4c9f967cbbd9c5706c0954091a8f5a8

083d36089e83a563e122ff2a585dab24bbacaa90696f78d3a60ee52aa4af0e42

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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