nodemon-gulpnpm
Advisory published Updated
nodemon-gulp is a confirmed malicious npm package (MAL-2026-10065) that typosquats a legitimate package to trick installs (malicious versions 3.1.14, 3.1.15, 3.1.16). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in nodemon-gulp (npm)
What this malware does
Package is published as nodemon-gulp but its contents are a verbatim copy of the upstream nodemon project: package.json declares author: Remy Sharp, homepage: https://nodemon.io, and bin: { "nodemon": "./bin/nodemon.js" }, so installing this package places a nodemon shim on the user's PATH supplied by an unrelated publisher. package.json also declares "ts-webplug": "3.0.5" as a runtime dependency, yet no file under lib/ or bin/ ever require()s ts-webplug. The only effect of declaring this dep is to silently pull ts-webplug into the installer's dependency tree on npm install, where its lifecycle and import-time code can execute. This is the canonical namespace-abuse + typosquat-loader shape: a clone of a well-known package, republished under a confusable name, used as a vehicle to deliver an otherwise-unjustified third-party dependency to anyone who installs it.
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
Search your lockfiles and build artifacts for nodemon-gulp (3 malicious versions).
If you installed it — respond
nodemon-gulp is a typosquat — you almost certainly intended a legitimately-named package. Remove nodemon-gulp, 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-gulp 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks nodemon-gulp-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.