Which versions of humunculous59101 are malicious?

The following PyPI versions of humunculous59101 are flagged malicious: 0.3.6. Treat any of these as compromised.

How do I remediate humunculous59101 if I installed it?

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

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

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

Malicious package

humunculous59101PyPI

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

MAL-2025-191635

Immediate action

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

pip uninstall humunculous59101

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.3.6

Indicators of compromise (SHA-256)

2ac3d66b1d490b1ca424232740ed5dcbbc0f7de35b2069500ad2bc96ea36d591

6827a1e29806ff5d9d21b5fe7026b95344d25af553b1ebb3074e0b76697b6c94

8a91be6e2afb95f2eeaf8f48eb0bf62bf737ba21ae56aee91c4c75c27a5ba21b

9f19cadbd6565168c3a786b573dfd7e965a41cf1c6ffd32bc4ce640e36548500

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

Campaign

RLMA-2025-056042025-10-wangzhou183RLUA-2026-00410

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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