Which versions of openseaz are malicious?

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

How do I remediate openseaz if I installed it?

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

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

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

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

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

Malicious package

openseazPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10080

Immediate action

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

pip uninstall openseaz

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)

d7f9dc22c3538800d73cd91cc4f0d550257c9b864117bb1c6fb91d3eb3bc53f9

f72157a69d9d45e7a11df572a6aebbc0bfe5f3514f28836913ac882ffecb7b9e

a31789670347d825788702cfbcd712b01db782414a3048fecd5afcc3ed7f22c6

c01eff0f71e284c6eb9182f95d578576177c3c2a2df8432ba60199db7cee651b

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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