MAL-2026-18284 Malicious code in @jm-telefonica/multibrand-components (npm)
Malicious package
Published
MAL-2026-18284 is a malicious package: @jm-telefonica/multibrand-components (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-18284/ (Markdown: https://insights.sbomify.com/MAL-2026-18284/index.md)
- Package
- @jm-telefonica/multibrand-components
- Registry
- npm
What is MAL-2026-18284?
MAL-2026-18284 is a malicious package in @jm-telefonica/multibrand-components, published on 25 Oct 2026.
Official description
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.What should I do about MAL-2026-18284?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.