Which versions of chroma-client are malicious?

The following PyPI versions of chroma-client are flagged malicious: 0.5.7. Treat any of these as compromised.

How do I remediate chroma-client if I installed it?

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

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

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

Malicious package

chroma-clientPyPI

chroma-client is a confirmed malicious PyPI package (MAL-2026-16143) that steals credentials and exfiltrates sensitive data (malicious version 0.5.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chroma-client (PyPI)

MAL-2026-16143

Immediate action

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

pip uninstall chroma-client

What this malware does

This package does not carry any malicious payload yet, but uses exactly the same technique as other packages from the campaign aiming to mislead LLM security tools.

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

Campaign: 2026-09-openaii

Reasons (based on the campaign):

Downloads and executes a remote malicious script.
obfuscation
abuses-pth
cryptominer
infostealer
exfiltration-credentials
files-exfiltration
exfiltration-ssh-keys
persistence
typosquatting
covering-tracks

Malicious versions

1 flagged

0.5.7

Indicators of compromise (SHA-256)

f74658ebb12f3a5cbf8577a768965f3ae81fbe8a156acc843ecffe3dfe2e5153

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

Campaign

2026-09-openaii

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks chroma-client-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

Explore

All malware advisories How O3 detects malware Vulnerability database