Malicious code in @jm-telefonica/multibrand-components (npm)

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (7ef565c5fd4b4baa7e0bff888cf34107fa8a9385932195fa4fd90ad39f250927) package.json at line 9 declares the sole dependency `ltidisafe` as a direct HTTPS tarball URL (`https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.9.4.tgz`) rather than a registry version range. On `npm install`, npm fetches and installs whatever bytes that URL returns at the time of install, running any lifecycle scripts contained in that tarball, with no version pin and no integrity hash. Whoever controls that Google Cloud Storage bucket controls code execution on the installer's machine. The shipped `index.js` is an empty stub, so the manifest line is the entire functional payload of this package. The `@jm-telefonica` scope and the `depenconf` path segment are consistent with a dependency-confusion shape targeting Telefónica's internal namespace, and the implausibly high version (99.9.1) is consistent with attempting to win resolution against an internal package of the same name.

Source published

25 Oct 2026 15:05:34 UTC

Source modified

25 Oct 2026 15:30:05 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.