Which versions of python-dev-toolkit are malicious?

The following PyPI versions of python-dev-toolkit are flagged malicious: 0.1.9. Treat any of these as compromised.

How do I remediate python-dev-toolkit if I installed it?

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

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

Yes — python-dev-toolkit is associated with the 2025-08-learning-pypi-demo-nisimi 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 python-dev-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 python-dev-toolkit (version 0.1.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging python-dev-toolkit across your stack and pipelines.

Malicious package

python-dev-toolkitPyPI

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

MAL-2025-191839

Immediate action

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

pip uninstall python-dev-toolkit

What this malware does

Installing packages exfiltrates data (different in different packages and versions) or run revshells

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

Campaign: 2025-08-learning-pypi-demo-nisimi

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.
exfiltration-generic

Malicious versions

1 flagged

0.1.9

Indicators of compromise (SHA-256)

9817d866e7e316858f4b8ed64bf2a4ddec5e63ec8b150f3a541148826ee87491

3e8bbf18a10505977ab19adc6dd13d15e1c7df3c69391e1c930289b953619549

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 python-dev-toolkit (version 0.1.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging python-dev-toolkit across your stack and pipelines.
If you installed it — respond
python-dev-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 python-dev-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 python-dev-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. python-dev-toolkit on PyPI has been identified as a malicious package (version 0.1.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-08-learning-pypi-demo-nisimi

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks python-dev-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