Which versions of cheeriobox are malicious?

The following npm versions of cheeriobox are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate cheeriobox if I installed it?

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

If cheeriobox 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.

Is cheeriobox part of a known attack campaign?

Yes — cheeriobox is associated with the IN-MAL-2026-010516 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 cheeriobox across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for cheeriobox (version 1.0.0).

Malicious package

cheerioboxnpm

Advisory published Jul 14, 2026Updated Jul 14, 2026

cheeriobox is a confirmed malicious npm package (MAL-2026-10585) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cheeriobox (npm)

MAL-2026-10585

Immediate action

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

npm uninstall cheeriobox

What this malware does

[email protected] is a delivery vehicle for install-time credential theft. package.json declares a postinstall hook that runs node.init.js, which enumerates roughly 60 credential-shaped environment variables (including NPM_TOKEN, GITHUB_TOKEN, AWS_SECRET_ACCESS_KEY, GCP, Azure, Stripe, and Docker tokens), reads home-directory secret files (~/.npmrc, ~/.env*, ~/config.json, ~/credentials.json), scans ~/.config for files matching token/cred/secret patterns, and collects host reconnaissance (os.hostname(), os.platform(), process.cwd(), process.pid, plus CI-detection flags such as CI/GITHUB_ACTIONS/GITLAB_CI). The collected data is POSTed as JSON to a hardcoded endpoint at webhook.cool (path /at/tender-deer-80/...). index.js exports an empty object, so the package has no legitimate library functionality — its only effect on install is credential exfiltration, with CI environments explicitly targeted.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

1160a4c1ee0340e9897a42a75d735750b7d92fc887bef135a5a979c371356df4

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for cheeriobox (version 1.0.0).
If you installed it — respond
cheeriobox 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 cheeriobox 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

No. cheeriobox on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010516

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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