Which versions of openwsea are malicious?

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

How do I remediate openwsea if I installed it?

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

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

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

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

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

Malicious package

openwseaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10090

Immediate action

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

pip uninstall openwsea

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)

c85fbec29fe1516be6d4dbb37f8ee9b716b49e9199679576bbe58c8dbe5f8ede

158950165cf4dfb54fb0268a3dc752367bdfbcb061dd8c775df165f877ca191f

b41936686650e4685b85dc0556d806c49ef458b2bfa2a25492c8b640a7098b1e

d07954f1304eb885372b599176dade8d027023d33a049c46c2f7cd4318038f80

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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