jm-telefonica-multibrand-components

Ecosystem: npm

Downloads:

Vulnerabilities from the last (months)
  • 0CriticalAffects 0 versions
  • 0HighAffects 0 versions
  • 0MediumAffects 0 versions
  • 0ModerateAffects 0 versions
  • 0LowAffects 0 versions
Severity distribution (all time)
0vulnerabilities
  • Critical0 (0.0%)
  • High0 (0.0%)
  • Medium0 (0.0%)
  • Moderate0 (0.0%)
  • Low0 (0.0%)

Monthly breakdown

  • 0 vulnerabilities
    • Critical: 0
    • High: 0
    • Medium: 0
    • Moderate: 0
    • Low: 0

Vulnerabilities (1)

Known vulnerabilities affecting jm-telefonica-multibrand-components, based on data from OSV.

Vulnerabilities affecting jm-telefonica-multibrand-components
IDSeveritySummaryAffected versionsPublishedSource
MAL-2026-18284UnknownMalicious 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
  • all
OSV (opens in a new tab)
  • MAL-2026-18284Unknown
    Malicious code in @jm-telefonica/multibrand-components (npm)
    • all

    --- _-= 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

Showing 1-1 of 1 vulnerabilities