Which versions of oepnsea are malicious?

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

How do I remediate oepnsea if I installed it?

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

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

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

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

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

Malicious package

oepnseaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10057

Immediate action

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

pip uninstall oepnsea

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)

b4c33678a1ead492f5eeb745ac0bc98dd7962f05bf93c680c54da26348385d04

4a21e25caf660cb2d97ac6ab71f3d0c9d014ea114d7afd328e29d4bd002e4352

2dfc506229ff91beaf18e569fbcb735c1dc9a37646ecd808b5420a096252cde7

60293c7383130abbcb626255e06ddab6c06f524bbedd04751bd79053e695cf69

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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