Which versions of opensew are malicious?

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

How do I remediate opensew if I installed it?

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

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

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

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

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

Malicious package

opensewPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10084

Immediate action

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

pip uninstall opensew

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)

9056d0881d4b53b5ee0850f9c82861a485b2ca749b4bfac12a06ed937d0c3da1

2a0cfbe606ccf3dcb6fd81c0bd0960b31b6d422c45c3a1be49af19b95fca4fe3

ffa6753393d986731290af6d134273da8701dc295fa7eea213ab0a78dd299246

bf2ebfbb8590fd5da5e1bee31e1ea5dcc4ac141f0f78f4758008c1cd02e4a67a

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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