Which versions of opwnsea are malicious?

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

How do I remediate opwnsea if I installed it?

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

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

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

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

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

Malicious package

opwnseaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10099

Immediate action

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

pip uninstall opwnsea

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)

a4093980c50ab613b2fa04671bebba91979bb0ccb01fedefa3e04a29b83016e8

4edeb14f87593664eab9c140b179b59f069a87df0dc1a34c2cd2e2c6bd89a0e2

4f70df8d1c347a280aafd4cec249c57ed1703806c6199b644b0062addac42d5b

de7e3fb965ee35e132f04f833e3c6712a69f988fe0ed2ddea95647ac3ae028aa

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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