nodemon-webnpm
nodemon-web is a confirmed malicious npm package (MAL-2026-10515) that typosquats a legitimate package to trick installs (malicious version 3.1.13). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in nodemon-web (npm)
What this malware does
nodemon-web copies the source of the popular nodemon package verbatim and reuses Remy Sharp's author metadata and the https://github.com/remy/nodemon.git repository URL, while publishing under a lookalike name from an unrelated account. package.json declares a runtime dependency on type-swap@^3.1.3 that is not required or imported anywhere in the package's own code; the real nodemon has no such dependency. Installing nodemon-web therefore silently resolves and installs type-swap into the consumer's node_modules under cover of a familiar name and impersonated maintainer identity, adding third-party code to the installer's dependency tree that the package itself never uses.
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
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nodemon-web (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-web across your stack and pipelines.
If you installed it — respond
nodemon-web is a typosquat — you almost certainly intended a legitimately-named package. Remove nodemon-web, 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-web 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-web 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-web-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.