Which versions of config-toolkit are malicious?

The following PyPI versions of config-toolkit are flagged malicious: 1.0.11. Treat any of these as compromised.

How do I remediate config-toolkit if I installed it?

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

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

Yes — config-toolkit is associated with the 2026-02-devtools-webhook-cicd-utils 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 config-toolkit across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for config-toolkit (version 1.0.11).

Malicious package

config-toolkitPyPI

Advisory published Feb 11, 2026Updated Feb 11, 2026

config-toolkit is a confirmed malicious PyPI package (MAL-2026-855) that steals credentials and exfiltrates sensitive data (malicious version 1.0.11). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in config-toolkit (PyPI)

MAL-2026-855

Immediate action

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

pip uninstall config-toolkit

What this malware does

During installation, package installs a script that listens for remote commands and executes them. The script is also added to autostart configuration and disguised as system application

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

Campaign: 2026-02-devtools-webhook-cicd-utils

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
peristence-autorun
The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.
obfuscation

Malicious versions

1 flagged

1.0.11

Indicators of compromise (SHA-256)

f672e0a6f875d710a8851da211ff30828bda3755c9f9aebcb56fd0430b134ae5

Detection & response playbook

Credential / info stealer

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

Campaign

2026-02-devtools-webhook-cicd-utils

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks config-toolkit-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