Which versions of hamubika are malicious?

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

How do I remediate hamubika if I installed it?

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

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

Yes — hamubika 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 hamubika across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for hamubika (version 1.0.0).

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

Malicious package

hamubikaPyPI

Advisory published Oct 19, 2025Updated Dec 3, 2025

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

Malicious code in hamubika (PyPI)

MAL-2025-191747

Immediate action

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

pip uninstall hamubika

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

1.0.0

Indicators of compromise (SHA-256)

e8dc8ea0579690475a6c26e19f35b6495f4eaba5309d69100adb1128286d53ba

c55b19e3a5ae01340f8c4aa8a68372eda1a6d5646f63a26658a1df75b4a2cf0c

Detection & response playbook

Malicious package

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

2025-10-wangzhou183

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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