nodemon-lint

Details

---
_-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (51b598671d8b4d96e826035c56685f7064e10dbcf7cf150e7ab4b2bd9194ad9a)
Package is published as `nodemon-lint` but its package.json, README, bin name (`nodemon`), homepage (nodemon.io), and source tree are a verbatim copy of Remy Sharp's `nodemon`. It declares two runtime dependencies — `regexp-ts@^2.1.7` and `chai@^4.4.1` — that the upstream nodemon does not ship and that are not `require()`d anywhere in `lib/` or `bin/`. Installing `nodemon-lint` by mistake therefore silently pulls those packages into the installer's dependency tree via npm's normal resolution, even though the lure tarball itself contains only legitimate nodemon code. The name is a 5-character extension of a top-tier registry package (`nodemon`), and the unused-dependency shape is consistent with using the lure as a delivery vehicle for whatever those transitive packages contain. The transitive packages themselves were not inspected here, so confirmation of their content is required before publishing a hard block.

## Source: ghsa-malware (e62de7b45c63185183f5fe120bd363a176f70cb28d4abfeec9a3686b320a0b96)
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.

Compromised versions (1)

• 3.1.15

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.