Which versions of opnsea are malicious?

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

How do I remediate opnsea if I installed it?

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

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

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

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

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

Malicious package

opnseaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10098

Immediate action

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

pip uninstall opnsea

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)

cd399b949546ec3cc1c1bd89e409ecb49a8c69abb8514b9fe062cde0208b29ba

2b81a855b90147af7acefbbcede1e10e5b8813e686b05b6fcb5a4a0fcff53b5c

033d437645cd5d1a96a500be8a66fae1693d11869c62a60e7357f6dda8db9226

44e524ba1270f2153bff4de8a9b42253466a9ea65f1305df9c2897e6fa5dd9f3

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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