NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

chalkdevxnpm

Advisory published Updated

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

Malicious code in chalkdevx (npm)

MAL-2026-10584
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall chalkdevx

What this malware does

package.json declares a postinstall hook that runs.init.js on npm install. The script enumerates ~65 credential and CI environment variables (NPM_TOKEN, GITHUB_TOKEN, AWS_SECRET_ACCESS_KEY, STRIPE_, DOCKER_, cloud provider tokens, private keys), reads home-directory credential files including ~/.npmrc, ~/.env*, config.json, and credentials.json, and scans ~/.config for files matching token/cred/secret patterns. Collected data — together with host identifiers (os.hostname(), os.platform(), cwd, pid) — is POSTed as JSON to a hardcoded https://webhook.cool/at/tender-deer-80/... endpoint, a public webhook-inspection service unrelated to any declared package purpose. The package's declared functionality is trivial (empty description, minimal index.js); the credential-harvesting postinstall is the package's actual behavior. The name resembles the popular chalk package.

Malicious versions

1 flagged
2.0.0

Indicators of compromise (SHA-256)

3e6c8e970ad81ccd02b4725232cbd0d145a20f08e42983097229563e35cac8ad

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for chalkdevx (version 2.0.0).

  2. If you installed it — respond

    chalkdevx 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.

  3. Did it already run?

    If chalkdevx 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. chalkdevx on npm has been identified as a malicious package (version 2.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010520

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks chalkdevx-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

chalkdevx (npm) malicious package — MAL-2026-10584 | O3 Security