Which versions of nodemon-delog are malicious?

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

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

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.

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

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

Yes — nodemon-delog is associated with the IN-MAL-2026-010348, GHSA-7gjf-8j8g-xm9p 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-delog 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-delog (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-delog across your stack and pipelines.

Malicious package

nodemon-delognpm

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

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nodemon-delog (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-delog across your stack and pipelines.
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.
Did it already run?
If nodemon-delog 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-delog 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-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database