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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for config-toolkit (version 1.0.11). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging config-toolkit across your stack and pipelines.

Malicious package

config-toolkitPyPI

Malicious code in config-toolkit (PyPI) Remove it immediately and rotate any exposed credentials.

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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for config-toolkit (version 1.0.11). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging config-toolkit across your stack and pipelines.
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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks config-toolkit before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

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