codebuff-clinpm
Advisory published Updated
codebuff-cli is a confirmed malicious npm package (MAL-2026-4533) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.4, 1.0.10, 1.0.11…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in codebuff-cli (npm)
What this malware does
The npm package codebuff-cli impersonates the legitimate codebuff package (README copied verbatim from the official CodebuffAI project) and relays authenticated Codebuff traffic — API key, source code, context and chat messages — to an attacker-controlled backend instead of codebuff.com.
These three versions are not part of the existing OSV record MAL-2026-4533 (Amazon Inspector):
- 1.0.4 and 1.0.10: the
binentry launches an embedded manipulated binary directly (no install hook); its default endpoint isfireworks-endpoint--57crestcrepe.replit.app(present in both the binary and its source-map). - 1.1.3: default backend
fireworks-api-backend.vercel.app; downloads the payload from a foreign GitHub repository and disables TLS certificate verification for the launched payload.
The package was previously disclosed by Amazon Inspector (MAL-2026-4533); this report extends the confirmed-malicious set with three additional versions, determined by static code and dataflow review of the published npm tarballs.
This report is scoped to the additional versions (1.0.4, 1.0.10, 1.1.3) not yet listed, to avoid duplicating the existing record.
The package name codebuff-cli impersonates the legitimate codebuff npm package; the README is copy-pasted from the official CodebuffAI project (it even instructs users to run npm install -g codebuff), but the published artifact is an unofficial fork. Three concrete installer-side harms are present:
- Silent relay of user data to a non-publisher backend. README and the bundled binary configure the default backend as
https://fireworks-api-backend.vercel.app(a personal Vercel deployment) instead of codebuff.com. Because this CLI is an AI coding agent, by-default usage transmits the user's source code, prompts, and command history to that endpoint. - TLS verification globally disabled.
cli/bin/codebuff.cjsline 201 spawns the codebuff binary withNODE_TLS_REJECT_UNAUTHORIZED=0, disabling certificate verification for every HTTPS connection the binary makes (auth, backend, model providers). Combined with the redirected backend, this allows MITM of all transmitted code/prompts/credentials with no warning. - Unverified binary fetch from a mutable personal-account release. If the bundled binary is missing,
cli/bin/codebuff.cjsquerieshttps://api.github.com/repos/Marcus-Mok-GH/codebuff-cli/releases/latest, downloadscodebuff-<platform>-<arch>to~/.codebuff/bin/, chmods 0755, and executes it — with TLS verification disabled and no hash/signature check. Thelatesttag is mutable and the publisher is a personal GitHub user, not the CodebuffAI org.
Attacker benefit is concrete and sustained: every prompt, code excerpt, and credential entered by an installer who followed the README's codebuff instructions is delivered to the publisher's infrastructure over an unverified TLS channel, with the additional ability to swap the executable at any time through the mutable latest release pointer.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for codebuff-cli (29 malicious versions).
If you installed it — respond
codebuff-cli 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 codebuff-cli was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- codelake Research · finder
Detect & block this
O3 blocks codebuff-cli-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.