Which versions of openeasea are malicious?

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

How do I remediate openeasea if I installed it?

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

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

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

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

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

Malicious package

openeaseaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10065

Immediate action

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

pip uninstall openeasea

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)

feab61c0765469a414f3bfa16da6b52c80e99a4ee85d5bd59d6a28892650019a

393d231e323f53982cc215556b43386b2d3aebf360140603f83f29ff239c233c

2fbc2861e34a7b4cb6df580e43c1f910cf82a1560467d77c311f4f6f57a7d46c

3b461b0e1b5a0d6cba4171fc276f4aa634abbde82e01e366624a633cfa9fd550

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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