Which versions of oenwsea are malicious?

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

How do I remediate oenwsea if I installed it?

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

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

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

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

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

Malicious package

oenwseaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10054

Immediate action

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

pip uninstall oenwsea

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)

0d60835b079eae8d7e95e472562918f7deb40ba5044c10f949ff3466a6894795

a58b8d187cfcd9162c4afa7e4735b3935e097d4c21a0083c3fe978dcc087b44f

0a74a609c04ef47eda0aacb9d2411b9273e76be24aca2032c019fda2d6ddbd8a

d206a0f4e641fefb7a7c8370b6015b2fef8dcc19082bbf6bc88f27fc69dbe027

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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