Which versions of humunculous591014 are malicious?

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

How do I remediate humunculous591014 if I installed it?

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

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

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

Malicious package

humunculous591014PyPI

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

MAL-2025-191636

Immediate action

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

pip uninstall humunculous591014

What this malware does

Package imitates Roblox API wrapper, but the only action is getting the public IP, suggesting it's a security research or malicious attempt

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

Indicators of compromise (SHA-256)

1874dea7a27579b87dff3b5e1f5fdc334e532ac692da0e38b82d985edb08cc11

f9b8b3ad3b50d351bcd308531155e7f502d5b841d15ba76cea893c7d4f6d91ed

c11577c61879e85aacda7ebb86fc8450c95b08a151e6a058b5ccbec46616c42d

2db4535cf16f3f452b71d5b48052264d476976d07e52ba7a3c1488d668233e57

5b93cb46cb1b3a61e53df8131921ffb5202b59d107b42a3cd3a128d06c424f42

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

Campaign

RLMA-2025-056052025-10-wangzhou183RLUA-2026-00411

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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