nodemon-copacknpm
nodemon-copack is a confirmed malicious npm package (MAL-2026-5308) that steals credentials and exfiltrates sensitive data (malicious versions 3.1.15, 3.1.16). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in nodemon-copack (npm)
What this malware does
The package is published as 'nodemon-copack' but its package.json wholesale impersonates the legitimate nodemon project: homepage is set to https://nodemon.io, author is set to 'Remy Sharp', repository points to github.com/remy/nodemon, and a 'nodemon' bin entry installs a nodemon command into the consumer's PATH. The lib/* sources are a near-verbatim copy of upstream nodemon. The manifest declares two runtime dependencies that are absent from upstream nodemon and are not referenced by any file shipped in this tarball: 'regex-js' (^1.1.5) and 'chai' (^4.4.1). A grep across lib/ and bin/ shows no require('regex-js') or require('chai'), so neither package serves any functional purpose here; their only effect is to be silently pulled into the installer's dependency graph by anyone who installs nodemon-copack believing it is a legitimate nodemon fork. chai is a test-assertion library normally placed in devDependencies; its presence in runtime dependencies, alongside the unreferenced regex-js, is consistent with a dependency-smuggling pattern where the actual payload would live in the smuggled package rather than in this one. No exfiltration, RCE, credential access, or install-time destructive action is present in the package itself; the harm shape is namespace impersonation plus transitive-dep injection, where the danger depends on what regex-js / chai resolve to at install time.
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 nodemon-copack (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nodemon-copack across your stack and pipelines.
If you installed it — respond
nodemon-copack 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 nodemon-copack 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 nodemon-copack 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 nodemon-copack-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.