Which versions of hawzebisdzazf are malicious?

The following PyPI versions of hawzebisdzazf are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate hawzebisdzazf if I installed it?

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

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

Yes — hawzebisdzazf is associated with the RLMA-2024-11058, GENERIC-standard-pypi-install-pentest, RLUA-2026-00379 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 hawzebisdzazf 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 hawzebisdzazf (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hawzebisdzazf across your stack and pipelines.

Malicious package

hawzebisdzazfPyPI

Malicious code in hawzebisdzazf (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11605

Immediate action

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

pip uninstall hawzebisdzazf

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package 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: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

9d7fdde10cbf1007825c96f67193c7ee09e394eb2dd1ee08f4761f854c2693d4

d49e8d8729dc84478178b201fce7ba56687a35ca34cc6a643aa248e2e13bc556

611fde1d6bc50a7046af0ed84bcd93554d152b5e83e8f80fc822eb038840c971

0fc0479b2f73678ec82cd96b97416d7f79c6487f176687a951662f16980f4f58

1afc4ac4d4b1d3c587da30f2084858f9f118f033f14f8c644fea478ad6d42969

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

Campaign

RLMA-2024-11058GENERIC-standard-pypi-install-pentestRLUA-2026-00379

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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