Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@jm-telefonica/multibrand-componentsnpm

Advisory published Updated

@jm-telefonica/multibrand-components is a confirmed malicious npm package (MAL-2026-18284) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-18284
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @jm-telefonica/multibrand-components

What this malware does

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.

Malicious versions

1 flagged
99.9.1

Indicators of compromise (SHA-256)

7ef565c5fd4b4baa7e0bff888cf34107fa8a9385932195fa4fd90ad39f250927

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @jm-telefonica/multibrand-components (version 99.9.1).

  2. If you installed it — respond

    Remove @jm-telefonica/multibrand-components from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If @jm-telefonica/multibrand-components was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @jm-telefonica/multibrand-components on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021692

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @jm-telefonica/multibrand-components-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore