NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

fakehuopPyPI

Advisory published Updated

fakehuop is a confirmed malicious PyPI package (MAL-2026-4749) that executes malicious code on install (malicious versions 3.1.0, 3.2.0, 3.5.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fakehuop (PyPI)

MAL-2026-4749
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall fakehuop

What this malware does

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.

Malicious versions

4 flagged
3.1.03.2.03.5.03.7.0

Indicators of compromise (SHA-256)

01b6d228f2f167f660bb588665de6df915cd05d025b201027962bfe1c493e808
677eed2b8b2630ec8e88b29d7ae3d9d49fc0d0c18230cc51b24d8102cdb151ee
c4e7b6565fad1e78a9aed6fcbf5e1992a05f51f0bbb46c0412f614b9777867f5
d09b228809877b9a10237ba3c8becd1b069c803096a35b8ac363321dee102dce

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for fakehuop (4 malicious versions).

  2. If you installed it — respond

    Remove fakehuop from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If fakehuop was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. fakehuop on PyPI has been identified as a malicious package (versions 3.1.0, 3.2.0, 3.5.0, 3.7.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004042IN-MAL-2026-004064IN-MAL-2026-004063IN-MAL-2026-004065

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks fakehuop-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

fakehuop (PyPI) malicious package — MAL-2026-4749 | O3 Security