Which versions of openasea are malicious?

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

How do I remediate openasea if I installed it?

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

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

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

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

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

Malicious package

openaseaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10063

Immediate action

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

pip uninstall openasea

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)

be532f6718161a6d86397f0297a4e7cb5695be43e056407da28e810f5fec99d0

76205c8befdcd8107ae90a994dd76c231e4ffbb10f760335c4bde17fe27c170b

8b341e2f737b2cdad14b88c66ceb936b962e81fc63fec719b11ac94275bc16ab

85d9b03d3818f9267346304c89d33a00576f1fac74acc8bbf6f6bbc496e6441f

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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