NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

nodemon-delognpm

Advisory published Updated

nodemon-delog is a confirmed malicious npm package (MAL-2026-10507) that steals credentials and exfiltrates sensitive data (malicious version 3.1.13). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nodemon-delog (npm)

MAL-2026-10507
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall nodemon-delog

What this malware does

nodemon-delog is published under a name that resembles the widely-used nodemon package and ships a verbatim copy of nodemon's source tree, README, homepage (nodemon.io), author (Remy Sharp), and repository metadata (github.com/remy/nodemon), presenting itself as the real project. Its package.json declares two runtime dependencies that upstream nodemon does not use and that no file under lib/ or bin/ references: type-atob and chai. Because these are declared under dependencies, they are resolved and installed into the consumer's node_modules on npm install nodemon-delog, regardless of the fact that nodemon-delog's own code never imports them. The lure package itself contains no exfiltration or RCE code; the harm mechanism is the forced resolution of the sibling packages into the installer's dependency tree, where their install/require-time code will execute. The impersonation of an established package, combined with the presence of runtime dependencies unrelated to the advertised functionality and unreferenced by any shipped file, is the dependency-smuggling lure pattern.

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

1 flagged
3.1.13

Indicators of compromise (SHA-256)

ea1c5b4054d6daffaf190005db661027e29255ae20de1bb410f506de1f178532
8fc60bc718b0034bfe43c31ab03ace3f0f205d90e2e89fd39a5d9710e72ab737

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for nodemon-delog (version 3.1.13).

  2. If you installed it — respond

    nodemon-delog 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.

  3. Did it already run?

    If nodemon-delog was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. nodemon-delog 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-010348GHSA-7gjf-8j8g-xm9p

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks nodemon-delog-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

nodemon-delog (npm) malicious package — MAL-2026-10507 | O3 Security