Which versions of huzzleuo130 are malicious?

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

How do I remediate huzzleuo130 if I installed it?

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

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

Yes — huzzleuo130 is associated with the RLMA-2025-05607, 2025-10-wangzhou183, RLUA-2026-00413 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 huzzleuo130 across my projects, lockfiles, and CI pipelines?

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

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

Malicious package

huzzleuo130PyPI

Advisory published Oct 19, 2025Updated Mar 19, 2026

huzzleuo130 is a confirmed malicious PyPI package (MAL-2025-191638) 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 huzzleuo130 (PyPI)

MAL-2025-191638

Immediate action

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

pip uninstall huzzleuo130

What this malware does

Packages that either reports home installation, simulate malicious activity or imitate Roblox API wrapper.

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)

f15e80fec413984aca617aedd46bf35837485b31cb201bfe60e45e393941e36a

8498a967441051b9b64b5c465d6abb8d37432a5b479b2522bca7aed61a1b7c5c

85df7f2dfe2955a251c0e1858049dab9b978d9812a067235cb04c6ffb25131fc

a01666eafc8e6c8ad1417bb315abb0d42a6917f651a832d426aeeef52f4f3eee

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for huzzleuo130 (version 0.1).
If you installed it — respond
Remove huzzleuo130 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 huzzleuo130 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. huzzleuo130 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

RLMA-2025-056072025-10-wangzhou183RLUA-2026-00413

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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