create-kumo-projectnpm
create-kumo-project is a confirmed malicious npm package (MAL-2026-11024) that steals credentials and exfiltrates sensitive data (malicious version 22.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in create-kumo-project (npm)
What this malware does
Package presents itself as a create-*-project scaffolder but ships no scaffolding functionality. The bin/run.js entry, invoked when a user runs npx create-kumo-project, performs a hardcoded HTTPS POST to https://deepbounty.dd06-dev.fr/cb/7a2d35ee-27c4-48a9-8f2d-457bc173b031 carrying the package name, a timestamp, a transport identifier, and the basename of INIT_CWD/CWD (the installer's project directory name). The description field in package.json self-labels this as a 'Security PoC for Bug Bounty', matching the npx / dependency-confusion research squatting pattern. Data volume is small (a project-directory basename, not credentials or filesystem contents) and the beacon only fires when a user explicitly invokes the bin via npx, not on npm install. No exfiltration of environment variables, credentials, filesystem contents, or persistence is present; no RCE or dropper. The concerns are: (a) the package occupies a create-kumo-project name to catch typos of a legitimate scaffolder, and (b) invoking it silently reports the victim's project name to a third-party endpoint. This is a bug-bounty proof-of-concept for name confusion, not a full-blown credential stealer, but it is a live beacon to an author-controlled URL directed at unsuspecting installers.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for create-kumo-project (version 22.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging create-kumo-project across your stack and pipelines.
If you installed it — respond
create-kumo-project 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-kumo-project 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-kumo-project 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks create-kumo-project-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.