Which versions of hugginglega are malicious?

The following PyPI versions of hugginglega are flagged malicious: 1.0, 1.1, 1.2, 1.3, 2.0. Treat any of these as compromised.

How do I remediate hugginglega if I installed it?

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

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

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

Malicious package

hugginglegaPyPI

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

MAL-2025-935

Immediate action

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

pip uninstall hugginglega

What this malware does

Importing the module downloads a script that then download and run an infected executable

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

Campaign: 2024-12-hugginglega

Reasons (based on the campaign):

Downloads and executes a remote executable.
Downloads and executes a remote malicious script.
dependency-confusion

Malicious versions

5 flagged

1.01.11.21.32.0

Indicators of compromise (SHA-256)

d5d590c6a3be8660ec718d66c7ff87f3fe4032a446572ba5a74553fb1757d9a5

0df3dbc3e25b09132ecba6253cc883619214f298e57c5f9db3932b89fd4bd387

50647cbe9ac6f4cf09b47c93b53cd292dc5d358f04f0efb1ccd5ba48dd58bc5d

29b87fe4b9030255c3ad4ef83b4ef42a99467cf800e0a2c8753873994d08ae12

08965fcd5a7be828ab0e73b3c22f718b00a6ccfbf0f1eb13c76dfa83fb98b5ea

decc88e0bb77bc450579b1e4b3d19e792605af91da07d20c099b2a046d9ee6a5

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

Campaign

RLMA-2025-004752024-12-hugginglegaRLUA-2026-00407

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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