live-detection-dashboard
Generate a random hex color
This report shows the evidence for live-detection-dashboard@100.0.0, the only known version.
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 23d ago · by lpm-firewall-aiThe source establishes automatic, unconsented export of identifying installation data unrelated to the package's color-generation functionality. This supports blocking for data exfiltration without claiming credential theft or remote execution.
Decision evidence
public snapshot- package.json automatically runs setup.js before installation and suppresses failure.
- setup.js collects the hostname, username, working directory, platform, architecture, Node version, and npm registry setting.
- setup.js posts the collected data to a fixed AWS API endpoint and silently ignores request errors.
- index.js only exports a random hexadecimal color generator.
- No credential harvesting, remote code execution, or filesystem mutation was found.
Source & flagged code
8 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgSource appears to send environment or credential material to an external endpoint.
Findings
Affected versions and remediation
This report applies to live-detection-dashboard@100.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing live-detection-dashboard@100.0.0. 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.