Which versions of openrsea are malicious?

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

How do I remediate openrsea if I installed it?

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

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

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

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

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

Malicious package

openrseaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10071

Immediate action

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

pip uninstall openrsea

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)

5a9a9b73cc259bc24cda2754f617ecd9b55cf07fc888f6959bed7b5ba06803a1

bbc7a8da7aba4100e793c326e9f1a93cd839f79ce3297679b2212100ba563408

e04ff75741a4680f509c1940b5dfa8c84a50ff0c00baf92769d7046b1262a74c

fea13ca4702dc7e0adeb0531318dbe17e8a5054186bd3baa6623ee0159c8c476

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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