Which versions of humunculous5910 are malicious?

The following PyPI versions of humunculous5910 are flagged malicious: 0.2.9, 0.3.1. Treat any of these as compromised.

How do I remediate humunculous5910 if I installed it?

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

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

Yes — humunculous5910 is associated with the RLMA-2025-05603, 2025-10-wangzhou183, RLUA-2026-00409 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 humunculous5910 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 humunculous5910 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging humunculous5910 across your stack and pipelines.

Malicious package

humunculous5910PyPI

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

MAL-2025-191634

Immediate action

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

pip uninstall humunculous5910

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

2 flagged

0.2.90.3.1

Indicators of compromise (SHA-256)

ecb71ae798f14821d5a4afac28c10e663a57218bd1f750e40bac7cd62baf4263

bfe0cc461bf49d1689c8b2e2d1580ccb86634ca9607ac9d4fca7e65b0f9b845e

653da18ccefceb9c2bc1dc858e100bcc242e88b449225e1c9337487da1af3826

ea3762b930a6b60cb01af7493844e96b9bc7cfe8874b9da723d90a518a29d48d

58a48b8c5f4c95fd1c67765df9c23b83ed72c5e5f4c99bee315476eea0386674

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for humunculous5910 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging humunculous5910 across your stack and pipelines.
If you installed it — respond
Remove humunculous5910 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 humunculous5910 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 humunculous5910 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. humunculous5910 on PyPI has been identified as a malicious package (versions 0.2.9, 0.3.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-056032025-10-wangzhou183RLUA-2026-00409

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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