Which versions of huggingfaces-hub are malicious?

The following PyPI versions of huggingfaces-hub are flagged malicious: 95.6. Treat any of these as compromised.

How do I remediate huggingfaces-hub if I installed it?

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

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

Yes — huggingfaces-hub is associated with the 2024-11-byted-dast 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 huggingfaces-hub 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 huggingfaces-hub (version 95.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging huggingfaces-hub across your stack and pipelines.

Malicious package

huggingfaces-hubPyPI

Malicious code in huggingfaces-hub (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-10728

Immediate action

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

pip uninstall huggingfaces-hub

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

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: 2024-11-byted-dast

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
typosquatting
dependency-confusion

The OpenSSF Package Analysis project identified 'huggingfaces-hub' @ 95.6 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

95.6

Indicators of compromise (SHA-256)

af0484bb217b7ddd004e70636121d72502d2f1cb891813befd59accc172d5b9d

c9d19f0ddad2b6d58448ac78c86818442db5643cd3067486de2aff318b29b876

030324e12766820002cc282dbac28f60bb0f2fc82d459e96c82f073a14e75592

9ca997255317a80120e07701813ac7266c6d07db1b9fbb6fc612ff84ff1cb990

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

Campaign

2024-11-byted-dast

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks huggingfaces-hub-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