Malicious code in @generic-means/ing-feat-scanner-libs (npm)

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (7053eaf141232704108519a3b3e7a0f1197d9eaabfa9fd3f4ff56ae9f753d763) package.json declares its sole dependency `ltidisafe` as a bare HTTPS tarball URL (`https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.9.3.tgz`) rather than a registry version range or a git ref pinned to a commit SHA. On `npm install`, npm fetches whatever bytes that URL currently returns and installs the resulting package, running any lifecycle scripts it contains. The tarball is unpinned, has no integrity hash, is not resolved through the npm registry, and the content at that URL can be swapped by whoever controls the storage bucket without any change to this package. The shipped `index.js` is an empty stub (`module.exports = {}`), so the off-registry dependency URL is effectively the entire payload delivered to installers. The dependency name does not correspond to a known npm package, and the storage.googleapis.com bucket is not an official registry endpoint.

Source published

25 Oct 2026 15:05:51 UTC

Source modified

25 Oct 2026 15:30:04 UTC

Observed here

25 Oct 2026 16:17:16 UTC

Source terms

OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.