Which versions of hamurico are malicious?

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

How do I remediate hamurico if I installed it?

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

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

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

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

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

Malicious package

hamuricoPyPI

Advisory published Oct 19, 2025Updated Mar 19, 2026

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

MAL-2025-191628

Immediate action

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

pip uninstall hamurico

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)

c3921036d42829dcedb7405f7556216d954edc9c25c69068221c78d43fde887b

2e78810e79974e248ac22833227c9f06afbc49b50e2e00243236e24b11bb7a3a

ae32a191b8b917707be1b631c022a7ffbc889b84937dc71700a0d6f589b65ad2

2309b69c4d1d74c43f19a3ddeb927a697a35100d54e33ade7e1a649c65c1449c

Detection & response playbook

Malicious package

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

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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