Which versions of shadokv are malicious?

The following PyPI versions of shadokv are flagged malicious: 912.6. Treat any of these as compromised.

How do I remediate shadokv if I installed it?

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

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

Yes — shadokv is associated with the 2024-11-byted-dast 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 shadokv across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for shadokv (version 912.6).

Part of a larger attack: 2024-11-byted-dast published 183 malicious packages. See the full campaign →

Malicious package

shadokvPyPI

Advisory published Nov 6, 2024Updated Dec 12, 2025

shadokv is a confirmed malicious PyPI package (MAL-2024-10459) that steals credentials and exfiltrates sensitive data (malicious version 912.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in shadokv (PyPI)

MAL-2024-10459

Immediate action

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

pip uninstall shadokv

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-11-byted-dast

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
typosquatting
dependency-confusion

The OpenSSF Package Analysis project identified 'shadokv' @ 912.6 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

912.6

Indicators of compromise (SHA-256)

d63b5bacf693f4e1797b1d80dc8abff1ac77c59101018141811201201aa55c77

a0a14ca391ee92eb30d0dc68236dae3ba9fe8fd0bd542b4b1286f73bc9315934

50a86371d91df819e5ed74554d58457de377043882b8ba9f98f71b7abfa006e4

441e1e2a7b18b8ee5f900f79cc3fef1e76f09a463375e0861fd3f2a05ace0456

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for shadokv (version 912.6).
If you installed it — respond
shadokv 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 shadokv 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. shadokv on PyPI has been identified as a malicious package (version 912.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2024-11-byted-dast

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

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