Which versions of hugchats are malicious?

The following PyPI versions of hugchats are flagged malicious: 0.4.9. Treat any of these as compromised.

How do I remediate hugchats if I installed it?

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

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

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

Malicious package

hugchatsPyPI

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

MAL-2024-12289

Immediate action

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

pip uninstall hugchats

What this malware does

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

Campaign: 2024-07-adfboba

Reasons (based on the campaign):

Malicious versions

1 flagged

0.4.9

Indicators of compromise (SHA-256)

d76dda76f3b94fa43c6560d3a57eebc537738e03f497ed7de257de6e2a0aebb5

172ccaf532e98b4ea6a98cdd9cb1cfb7b7f1b0efd593217f28d5a6b825edc1c1

e4bfbe9f2194cca2cb784d74d29901524f2a42c937696e23e0129964f545a724

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

Campaign

2024-07-adfboba

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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