Which versions of chalk-pack are malicious?

The following npm versions of chalk-pack are flagged malicious: 1.0.4, 2.0.0. Treat any of these as compromised.

How do I remediate chalk-pack if I installed it?

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

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

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

Malicious package

chalk-packnpm

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

MAL-2026-3754

Immediate action

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

npm uninstall chalk-pack

What this malware does

Package is named chalk-pack (impersonating chalk) with keywords and index.js impersonating lodash; index.js is a stub that self-describes as 'Just a dummy module. The real payload is in postinstall.js'. On npm install, postinstall.js executes a two-part stealer: (1) credential harvester — reads ~/.npmrc, ~/.env, and ~/.git-credentials, extracts npm auth tokens (npm_[a-zA-Z0-9]{36} and //registry.npmjs.org/:_authToken=...), and scrapes environment variables shaped like tokens/API keys/DB URLs/cloud/payment credentials; (2) crypto-wallet stealer — iterates 71 hardcoded Chromium/Brave/Edge/Firefox extension IDs for MetaMask, Phantom, Coinbase, Trust, Binance, OKX, Ledger, Trezor, Rabby, Keplr, Solflare, BitKeep, etc., reads Local Extension Settings/<extId>/*.log, regex-matches vault, seed, mnemonic, privateKey, and encrypted wallet JSON, and also walks ~/Documents, ~/Desktop, ~/Downloads for BIP39-word-count-matching files. All collected data is POSTed as JSON to http://149.28.127.35:8888 (plaintext HTTP, bare IP) hardcoded in const C2=process.env.C2_URL||'http://149.28.127.35:8888' at postinstall.js:7. The file header advertises itself as 'Token harvester + Crypto wallet scanner / Runs on npm install. Silent. Zero trace.' and every fs/http call is wrapped in try{}catch(e){} to suppress errors. Multiple independent attack fingerprints co-occur: hardcoded C2 in a lifecycle hook, installer-secret credential-file reads, wallet extension ID list, BIP39 seed-phrase scanner, and typosquat of a top-registry package — each independently sufficient.

Malicious versions

2 flagged

1.0.42.0.0

Indicators of compromise (SHA-256)

3e6eab5e9e696250cc719b36e144f4534cac2b38a25521cda80222b6c66cd64c

fb5b1dd23f490f87a1017ccfaf83acc738ad2fcf296016e958d9c2faeb921792

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

Campaign

IN-MAL-2026-002647IN-MAL-2026-002808

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks chalk-pack-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