Which versions of nodemon-elint are malicious?

The following npm versions of nodemon-elint are flagged malicious: 3.1.13. Treat any of these as compromised.

How do I remediate nodemon-elint if I installed it?

nodemon-elint is a typosquat — you almost certainly intended a legitimately-named package. Remove nodemon-elint, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed nodemon-elint — how do I know if it already compromised me?

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

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

Malicious package

nodemon-elintnpm

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

MAL-2026-10508

Immediate action

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

npm uninstall nodemon-elint

What this malware does

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

Malicious versions

1 flagged

3.1.13

Indicators of compromise (SHA-256)

869b2e1ce23c7668369cd6316bca7d3f8a564fa575ebbee8d1e3cf6a68d4ccaa

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nodemon-elint (version 3.1.13). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nodemon-elint across your stack and pipelines.
If you installed it — respond
nodemon-elint is a typosquat — you almost certainly intended a legitimately-named package. Remove nodemon-elint, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If nodemon-elint 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-elint 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. nodemon-elint on npm has been identified as a malicious package (version 3.1.13 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010347

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks nodemon-elint-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.

Malware detection Runtime egress monitoring