Which versions of oenasea are malicious?

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

How do I remediate oenasea if I installed it?

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

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

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

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

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

Malicious package

oenaseaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10050

Immediate action

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

pip uninstall oenasea

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)

5deeba760b858aa30456a4e926cdb8e7b5cc375844c2f4c85764042dded621b5

61cd316da681d5bf21ef1ed6f54fdd59847a56e77a1de56b9c729aa672f66252

984cb125e77ec44c2064b9b147f014bf467873af4d417580e7b23057fa01cd48

352f4e97f398fbf5d222c14efefc3898a20c7f8db54169fe324b17bcdbb04570

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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