Which versions of humunculous5910145 are malicious?

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

How do I remediate humunculous5910145 if I installed it?

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

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

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

Malicious package

humunculous5910145PyPI

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

MAL-2025-191637

Immediate action

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

pip uninstall humunculous5910145

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)

b6ffe72178d3a2c5f62c4d349ef701da0633c60cf08309bfb860bf5f97026813

932771b9bf6cf339ec2824c458e08cbc334d93a645a91343865130176e5b9b35

42aa1f0acca970dd3dd66bb2d709b7afadf6b3f70f24992dc69c5254482604f1

91f58103d3ecd630228f03405c999e8a199133a4feb45e7ae0bfd562b58bb181

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 humunculous5910145 (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging humunculous5910145 across your stack and pipelines.
If you installed it — respond
Remove humunculous5910145 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 humunculous5910145 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 humunculous5910145 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. humunculous5910145 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-056062025-10-wangzhou183RLUA-2026-00412

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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