Which versions of opemsea are malicious?

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

How do I remediate opemsea if I installed it?

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

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

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

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

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

Malicious package

opemseaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10060

Immediate action

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

pip uninstall opemsea

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)

2cd9658eabaa88485f14785929ed9d29c57d6390d283cbb183d00b88ac1094dd

fbb61ccf97d5967e2e171d6ba5de058474deee0bad1b09e89363c291f8ada0fd

bc39cb336ad6dd3db63ed315a6baf147f46f2c3f7bfd372c34718a1fcb815700

659314a370e091eee2a2a864d37e8f3059dfd3bbde2edbc1e27e1cabdd5fa42c

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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