Which versions of create-kachow are malicious?

The following npm versions of create-kachow are flagged malicious: 1.2.0. Treat any of these as compromised.

How do I remediate create-kachow if I installed it?

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

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

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

Malicious package

create-kachownpm

Malicious code in create-kachow (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4539

Immediate action

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

npm uninstall create-kachow

What this malware does

bin/create-kachow.js declares a BUILTIN_KEYS object containing live API keys for four third-party AI providers (Gemini key starting AIzaSyByPyGWXRVsa0..., OpenRouter sk-or-v1-673e3b6d..., Mistral OiCiNtvBsogE..., DeepSeek sk-7ecd4ed8...). The key-resolution helpers (e.g. resolveGeminiKeys) fall back to these built-in keys whenever the corresponding env var is unset, so any installer running npx create-kachow obtains and uses live credentials against generativelanguage.googleapis.com, openrouter.ai, api.mistral.ai, and api.deepseek.com. Two installer-affecting harms follow: (1) the keys are extractable from the package by anyone who installs it and can be abused against the four third-party providers (credential redistribution); (2) the README advertises a 'deterministic template generator — no AI required' fallback when no keys are set, but the code instead silently routes the user-supplied app description (the appPrompt from ask("Describe your app:")) to those four providers under the author's account, where prompts may be logged. This contradicts documented behavior and makes the data flow non-consensual.

Malicious versions

1 flagged

1.2.0

Indicators of compromise (SHA-256)

b65b2deeeafefb22b81e6a863b51115953b108991e5462d939dce3d6b8ee4a97

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

Campaign

IN-MAL-2026-003617

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks create-kachow-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