nodemon-lintnpm
nodemon-lint is a confirmed malicious npm package (MAL-2026-5309) that executes malicious code on install (malicious version 3.1.15). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in nodemon-lint (npm)
What this malware does
Package is published as nodemon-lint but its package.json, README, bin name (nodemon), homepage (nodemon.io), and source tree are a verbatim copy of Remy Sharp's nodemon. It declares two runtime dependencies — regexp-ts@^2.1.7 and chai@^4.4.1 — that the upstream nodemon does not ship and that are not require()d anywhere in lib/ or bin/. Installing nodemon-lint by mistake therefore silently pulls those packages into the installer's dependency tree via npm's normal resolution, even though the lure tarball itself contains only legitimate nodemon code. The name is a 5-character extension of a top-tier registry package (nodemon), and the unused-dependency shape is consistent with using the lure as a delivery vehicle for whatever those transitive packages contain. The transitive packages themselves were not inspected here, so confirmation of their content is required before publishing a hard block.
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
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nodemon-lint (version 3.1.15). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nodemon-lint across your stack and pipelines.
If you installed it — respond
Remove nodemon-lint from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If nodemon-lint 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-lint 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-lint-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.