Which versions of opensead are malicious?

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

How do I remediate opensead if I installed it?

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

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

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

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

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

Malicious package

openseadPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10076

Immediate action

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

pip uninstall opensead

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)

dabc896473a2a68ba70375e57e98f164d9f0975affad1bcab66e358f61c21d28

27ee698f2efbd5f097344e9a35126d66df0da6b4d53388de7544706438e955d8

79125d2c56a6cc9ddd836fad401e20ee6a039a7c430be6673680971497d91225

c4bf9624fac1227c3a285df9916473f53ad50b2f29f0eed45d57166bab7d646b

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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