Which versions of kcvlib are malicious?

The following PyPI versions of kcvlib are flagged malicious: 1.0.0, 1.0.1, 1.1.0, 1.2.0, 1.2.1, 1.3.0, 1.4.0. Treat any of these as compromised.

How do I remediate kcvlib if I installed it?

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

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

Yes — kcvlib is associated with the 2026-04-kcvlib 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 kcvlib across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for kcvlib (7 malicious versions).

Malicious package

kcvlibPyPI

Advisory published Apr 28, 2026Updated Apr 28, 2026

kcvlib is a confirmed malicious PyPI package (MAL-2026-3131) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.1.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in kcvlib (PyPI)

MAL-2026-3131

Immediate action

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

pip uninstall kcvlib

What this malware does

During import, the package downloads and executes obfuscated code. It appears to be an infostealer framework

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-04-kcvlib

Reasons (based on the campaign):

obfuscation
Downloads and executes a remote malicious script.
infostealer

Malicious versions

7 flagged

1.0.01.0.11.1.01.2.01.2.11.3.01.4.0

Indicators of compromise (SHA-256)

4a441a8e0abdd54964ca9e0a5e3a1d0e0c0435f05d80ab9e9210e10194a16f3d

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for kcvlib (7 malicious versions).
If you installed it — respond
kcvlib 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 kcvlib 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. kcvlib on PyPI has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.1.0, 1.2.0, 1.2.1, 1.3.0, 1.4.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-04-kcvlib

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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