Which versions of opensee are malicious?

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

How do I remediate opensee if I installed it?

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

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

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

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

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

Malicious package

openseePyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10081

Immediate action

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

pip uninstall opensee

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)

a700c709c680005d7976b7d0f474a1159f6ec7fa3a6d174e1154f94e8f4f61fd

f89a70fd6982f07fead8a0f0e1e257dfc3109925a862c57025eaa4352fee3976

793144f095ed4a16c4132da20fbb992dc890ff1df9926b440d0f25ab61ab3dd7

9fabb2ea206d9d2f6cee85b2429185d1b9a207337e937698770c6189f09aa1dc

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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