Which versions of openseae are malicious?

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

How do I remediate openseae if I installed it?

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

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

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

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

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

Malicious package

openseaePyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10077

Immediate action

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

pip uninstall openseae

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)

1621accd71d81a90b8293dfed6bdc90343e5517984442ea81c39178f179fdf47

d86155810e2f9fa4ca246708e9bb79fcc91a0b056bddb5c385f82ae23dd307c5

bb43a8865c5902deb419bbb558c242b5f9e441e94e4789784b5cc82cad02172a

987047337ed22e7c098f566be298fe557f852d72ff2ac4a2414924b0fe2d798e

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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