Which versions of openseaa are malicious?

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

How do I remediate openseaa if I installed it?

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

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

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

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

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

Malicious package

openseaaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10075

Immediate action

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

pip uninstall openseaa

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)

57eff135d750dd025ef713ed477b2cd8c0d8dcfda84cdabceb61533a347626c0

ac88763fdcaa1824cd06ef8eef470bbb06c117ec8b20b2f2ab597f4979c66d0c

5428b21b872ea57a73c1e7932fa333e90bb7c42f3a7b72f29569005158d1fc34

6e31a99a9705c1fab50576554465b9bed0925feee49af8b08d9e305a44383da3

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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