Which versions of oopensea are malicious?

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

How do I remediate oopensea if I installed it?

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

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

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

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

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

Malicious package

oopenseaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10058

Immediate action

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

pip uninstall oopensea

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)

f0b9f3b09359fc60a672940b625d0da0f17beea38d638d69e4b7add88a7332ee

3b24bc98ce44145eb012de9166ee90ad3af09edd311785273d2b1a774c1588f0

9400a8b0c9b0c8218eb8376d62c512c8c50c8cb1f1fa54a310c6aa5d17e14e0b

cdd7213d15b431f5bd0c3afaa7a784fc264c1ac1605bed583cca894a59b0a33f

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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