consumerweb-creditcollection
This report shows the evidence for consumerweb-creditcollection@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 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-13441 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 inspected source contains no direct attack behavior, but the remote tarball dependency leaves a material uninspectable install-time code path. This warrants a warning rather than a block.
Independent scan evidence
public snapshot- package.json declares ltidisafe from a remote tarball URL.
- The package's only functional install-time supply-chain path is that external dependency.
- package.json has no preinstall, install, or postinstall hook.
- index.js only exports an empty object.
- No credential access, shell execution, file writes, or exfiltration exists in the inspected source.
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-creditcollection@99.9.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing consumerweb-creditcollection@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.