Which versions of kimichat are malicious?

The following PyPI versions of kimichat are flagged malicious: 0.1.0, 0.1.1. Treat any of these as compromised.

How do I remediate kimichat if I installed it?

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

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

Yes — kimichat is associated with the 2026-07-kimichat, IN-MAL-2026-011104, IN-MAL-2026-011105 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 kimichat 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 kimichat (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kimichat across your stack and pipelines.

Part of a larger attack: 2026-07-kimichat published 8 malicious packages. See the full campaign →

Malicious package

kimichatPyPI

kimichat is a confirmed malicious PyPI package (MAL-2026-10864) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in kimichat (PyPI)

MAL-2026-10864

Immediate action

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

pip uninstall kimichat

What this malware does

The package presents itself as a 'Python wrapper for the bundled kimichat runtime' and exposes a kimichat-run console script plus kimichat.run(). Invoking either causes kimichat.core.run() to spawn bash on the bundled src/kimichat/resources/start.sh, which chmod+x's and executes a ~32MB bundled Linux ELF at src/kimichat/resources/kimichat. String analysis of the ELF identifies it as 'ForgeMiner/1.4.1', a stratum GPU miner with CUDA kernels for kawpow/xelis/kryptix/alpha/keryx and standard stratum verbs (mining.authorize, mining.subscribe). start.sh hardcodes the mining destination and wallet: FORGE_WALLET="prl1p2jan4dvkdfkt5r3pra7z96axrxjyjcgat9w7ldetlcy9wffm569sc9ux2t" and POOL="45.151.62.119:3361". Running the tool consumes the host's GPU and electricity and routes the mined rewards to the hardcoded author wallet; the delivered binary does not match the package's advertised purpose as a chat runtime.

In this campaign, packages use names similar to popular services (e.g. Kimi AI) to deploy cryptominer.

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

Campaign: 2026-07-kimichat

Reasons (based on the campaign):

cryptominer

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

1d4795d0466af3e087dba2ac688463000092f9f4fda9040a4653956a3dc2583a

dd54b31f9655bf3fdce1f88945d472f25a93b3da9ecc8b4370025842aa82689a

59d3c008ba7e9dad4a57424b2ded5748db91362d8a7b5bb6b9d3e2bceefe262c

b57c88bce76fccb6cb2b3a99ef53a62402a8d56b4918ba4c7f2b634036317093

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

Campaign

2026-07-kimichatIN-MAL-2026-011104IN-MAL-2026-011105

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

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