Which versions of huzzleup are malicious?

The following PyPI versions of huzzleup are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate huzzleup if I installed it?

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

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

Yes — huzzleup is associated with the 2025-10-wangzhou183 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 huzzleup across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for huzzleup (version 0.1).

Part of a larger attack: 2025-10-wangzhou183 published 19 malicious packages. See the full campaign →

Malicious package

huzzleupPyPI

Advisory published Oct 19, 2025Updated Dec 3, 2025

huzzleup is a confirmed malicious PyPI package (MAL-2025-191762) that executes malicious code on install (malicious version 0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in huzzleup (PyPI)

MAL-2025-191762

Immediate action

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

pip uninstall huzzleup

What this malware does

Package simulates malicious activity during installation and has no other purpose

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: 2025-10-wangzhou183

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.1

Indicators of compromise (SHA-256)

e038d21942743273805d886789934d4d5c7f500bf56e7829ac68595c61ea6bed

96519e802e0761cc6f22ffc2dde7aee04fc6806f5831c1e98c15512792a3cd1d

Detection & response playbook

Malicious package

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

Campaign

2025-10-wangzhou183

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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