MAL-2026-10508 Malicious code in nodemon-elint (npm)
Malicious package
Published
MAL-2026-10508 is a malicious package: nodemon-elint (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-10508/ (Markdown: https://insights.sbomify.com/MAL-2026-10508/index.md)
- Package
- nodemon-elint
- Registry
- npm
What is MAL-2026-10508?
MAL-2026-10508 is a malicious package in nodemon-elint, published on 13 Jul 2026.
Official description
[email protected] copies the source tree, README, author metadata, and homepage of the legitimate
nodemon package but is published under a confusable name. Its package.json declares a runtime dependency on type-elint@^3.3.7, which is not required or imported by any file under lib/ and has no documented purpose in the package. Installing nodemon-elint therefore causes npm to resolve and install type-elint into the installer's dependency tree, where any install-time lifecycle scripts or require-time side effects in that sibling package execute on the installer's machine. The package.json also lists chai@^4.4.1 — a test assertion library — under dependencies rather than devDependencies, with no require('chai') anywhere in lib/, an additional anomalous production dependency inconsistent with upstream nodemon. The pattern (name-confusion wrapper of a popular package + undocumented, unused sibling dependency whose name mirrors the typosquat scheme) is a dependency-chain drop: the wrapper itself contains no visible payload, but installing it pulls in attacker-controlled code via the forced dependency.What should I do about MAL-2026-10508?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.