nodemon-gulp (npm) · Malicious Code
Affects nodemon-gulpSource GCVE Database
Malicious package : remove nodemon-gulp and rotate any secrets on hosts that installed it.
Data as of 12 Jul 2026, 09:18 UTC
Malicious package
Published to npm · OSV MAL-2026-10065
What to do
Remove nodemon-gulp from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmnodemon-gulp | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (18cfb051ae84a8ed00bba3ae1eaf7720ec6479a402ae0540c6d66a7fa304f52a) 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. ## Source: ghsa-malware (bf7d5e881aed308912128dc41892a1e12dbedfd29ced5195ff2078be80dc6302) 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.