@jm-telefonica/multibrand-components@99.9.1
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe dependency's automatic preinstall discloses identifying environment data to a fixed, unrelated OAST endpoint. This verified installation-time disclosure supports blocking publication.
Decision evidence
public snapshot- The package manifest installs a dependency from a remote tarball.
- The dependency runs a script automatically during preinstall.
- That script hex-encodes the machine hostname, home directory, and username, then calls the request helper with each value.
- The helper places each value in a subdomain of a fixed OAST endpoint and sends an HTTP request to it.
Source & flagged code
7 flagged · loading sourceThe package manifest installs a dependency from a remote tarball.
package.jsonView on unpkg · L10Package manifest contains a dependency pinned to a remote tarball URL.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @jm-telefonica/multibrand-components@99.9.1.
See all versions of @jm-telefonica/multibrand-components for other recorded verdicts.
- Avoid installing @jm-telefonica/multibrand-components@99.9.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.