Which versions of huangpy are malicious?

The following PyPI versions of huangpy are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate huangpy if I installed it?

huangpy is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed huangpy — how do I know if it already compromised me?

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

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

Malicious package

huangpyPyPI

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

MAL-2024-11610

Immediate action

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

pip uninstall huangpy

What this malware does

Importing the module starts an infostealer attempting to exfiltrate webbrowsers' data to a Telegram webhook.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2024-10-huangpy

Reasons (based on the campaign):

infostealer
A Telegram webhook is used to send collected data.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4ade1f35e32ba342e00a56f82fba0562825ee6968971a95a8caddf6dd07426d8

f3a7a271534fcd374509e881fd46128be47369d7f4e24f36a9b3a67177846b53

a914c7e2cc097ba21e12b61f176cefd1971bb2a38f3b5fe2e81038e143f27da9

e5163e8a76f0e98522ce5e9ce159efe8925744c44f68e90a84f42d826c2e85f9

c7cff34c611fb59e2ed8a985d30b963ef0a6d3760444548e3dc975d5479ccb04

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for huangpy (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging huangpy across your stack and pipelines.
If you installed it — respond
huangpy is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If huangpy 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 huangpy 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. huangpy on PyPI has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-110632024-10-huangpyRLUA-2026-00404

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks huangpy-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring