Which versions of demozecox are malicious?

The following PyPI versions of demozecox are flagged malicious: 0.0.0. Treat any of these as compromised.

How do I remediate demozecox if I installed it?

Remove demozecox from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed demozecox — how do I know if it already compromised me?

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

Yes — demozecox is associated with the GENERIC-simple-tests 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 demozecox across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for demozecox (version 0.0.0).

Malicious package

demozecoxPyPI

Advisory published Mar 8, 2026Updated Mar 8, 2026

demozecox is a confirmed malicious PyPI package (MAL-2026-1285) that executes malicious code on install (malicious version 0.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in demozecox (PyPI)

MAL-2026-1285

Immediate action

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

pip uninstall demozecox

What this malware does

Packages that might be part of testing for pentesting / malicious activity / joy, with suspicious activity that does not present any real harm.

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: GENERIC-simple-tests

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

0.0.0

Indicators of compromise (SHA-256)

b32c6e6d2566a58b9a104d162c060982bff488fa547fb706c43553d0b7185ccb

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for demozecox (version 0.0.0).
If you installed it — respond
Remove demozecox from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If demozecox 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. demozecox on PyPI has been identified as a malicious package (version 0.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-simple-tests

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

O3 blocks demozecox-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database