consumerweb-calurls
This report shows the evidence for consumerweb-calurls@99.9.1. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
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.
OpenSSF/OSV Malicious Advisory
imported 2mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-10970 confirms this npm version as malicious.
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
The direct remote dependency is a real supply-chain risk, but reviewed package code is inert and has no lifecycle hook or concrete malicious behavior. Warn pending inspection of the referenced archive.
Independent scan evidence
public snapshot- package.json:10 installs ltidisafe from a direct remote tarball URL.
- The package’s only functional install-time effect is pulling an uninspected external archive.
- index.js only exports an empty object.
- package.json has no preinstall, install, postinstall, or prepare hook.
- No other package files, execution primitives, harvesting, or exfiltration code were present.
Source & flagged code
1 flagged · loading sourcePackage manifest contains a dependency pinned to a remote tarball URL.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to consumerweb-calurls@99.9.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing consumerweb-calurls@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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.