Which versions of oensea are malicious?

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

How do I remediate oensea if I installed it?

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

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

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

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

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

Malicious package

oenseaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10052

Immediate action

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

pip uninstall oensea

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)

06bac45bd5f1b46543599b943fe353feb88baa1fb15d2b242fe5481c4f3606ea

0e167794124f19d46529f80ecb7570b16697dba3aa96e6f30755f949e7180bcc

a0efb4f6e87bca0629e97a756fddb4692f68c6b61b8f2e0f74de16b91a3f4900

e4f450bab298b984beaf8a871be74100495a9832c1635c0f8168524db995cb60

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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