What does the huggingleg2 malware do?

Installing the package starts a revshell Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2024-12-huggingleg2 Reasons (based on the campaign): - The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine. - The package overrides the install command in setup.py to execute malicious code during installation.

Which versions of huggingleg2 are malicious?

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

How do I remediate huggingleg2 if I installed it?

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

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

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

Malicious package

huggingleg2PyPI

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

MAL-2025-934

Immediate action

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

pip uninstall huggingleg2

What this malware does

Installing the package starts a revshell

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

Campaign: 2024-12-huggingleg2

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.
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)

c3d2d113b69ab7c811fd32de5f831f98c73976e678425f05c61747b81078f1a9

b5db7f765f02adaa83c6f464ec54339279b949420281dfa726e684715f5fe232

19ba00b8fab08e8016af3bfb4ba9fbb18510b2aa823dfb82a46a5b3ecd477655

6ba90df2440613af1727c5b46a669b1bc6f196fc46667d87c39157d5e96a05e3

b66ac6e1c28ec210cb2a33b33021d65fa2a25fe2c7f8a64039bd109d1b3f1854

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

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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