MAL-2026-4749 Malicious code in fakehuop (PyPI)
Malicious package
Published
MAL-2026-4749 is a malicious package: fakehuop (PyPI). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-4749/ (Markdown: https://insights.sbomify.com/MAL-2026-4749/index.md)
- Package
- fakehuop
- Registry
- PyPI
What is MAL-2026-4749?
MAL-2026-4749 is a malicious package in fakehuop, published on 21 May 2026.
Official description
Every advertised function in this package (ask_llm, pink, america, iran, momo, abc, bcd, code, sf, liti, koko, init, dropnull, hellp, lc) instantiates a Groq client using a hardcoded
gsk_... API key owned by the package author and forwards the caller-supplied prompt argument to api.groq.com via client.chat.completions.create. Callers cannot supply their own key; the public API has no parameter or env-var override. As a result, any prompt content passed into these functions — which may contain proprietary data, customer input, or secrets — is routed through the author's Groq account, where the author can read it via their dashboard. 17 distinct hardcoded Groq keys are shipped across ai_helper.py, abc.py, america.py, bcd.py, code.py, dropnull.py, hellp.py, init.py, iran.py, koko.py, lc.py, liti.py, momo.py, pink.py, and sf.py. The package metadata reinforces the assessment: README references an unrelated sample_package with add/greet examples that don't exist in the source, the package and module names are nonsensical, and there is no documented legitimate purpose for the relay.What should I do about MAL-2026-4749?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.