Which versions of opnesea are malicious?

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

How do I remediate opnesea if I installed it?

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

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

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

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

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

Malicious package

opneseaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10097

Immediate action

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

pip uninstall opnesea

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)

71da3e4443f2eabdc8dce1f0c782e5fbe92ba5f80329c65e66a7f498efc41fd2

5e8b2a8229a47054c38b5e8024337a9a7ba23be0ed8c36b503625ec80df5eea7

56c0b9137145905e04d536383d4df93042c3742d8d6f8d9f11dec421342d87f7

3299f5b495591d65d1ce461fd348ee569dac3a4a885df7189e57ae4ebb076697

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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