Malicious code in live-detection-dashboard (npm)

CISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.

No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.

live-detection-dashboard is a dependency-confusion package: it takes a name that looks like an internal project, uses an inflated version (100.0.0) so it outranks private-registry versions, and runs `node setup.js || true` as a preinstall script on npm install. setup.js sends the hostname, username, working directory, OS, architecture, Node.js version and configured npm registry, with a per-package tracking token, in an HTTPS POST to `https://s85r5k14qk.execute-api.us-east-1.amazonaws.com/prod/hook`. The npm account amel10 published live-detection-dashboard and 9 similar packages within two minutes on 2026-09-30, all with the same setup.js. --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (5d6433d908aabd1002455fbed5a7afdf730c557f6c072fed817d76cad31a5ccb) The package's `preinstall` lifecycle script fires automatically on `npm install` and issues an HTTPS POST to the hardcoded endpoint https://s85r5k14qk.execute-api.us-east-1.amazonaws.com/prod/hook, carrying a JSON body composed of installer-side identifiers: os.hostname(), os.userInfo().username, process.cwd(), process.platform, process.arch, the Node.js version, and the configured npm registry, along with a static token. The advertised functionality of the package is a trivial random-hex helper, which does not require network activity or host/user identifiers, and the data flow is neither documented nor caller-configurable. The destination is an author-controlled AWS API Gateway. Package version 100.0.0 combined with a minimal declared purpose and an install-time beacon is consistent with a dependency-confusion / reconnaissance payload targeting internal build environments.

Source published

30 Sep 2026 07:11:22 UTC

Source modified

4 Oct 2026 23:45:18 UTC

Observed here

24 Oct 2026 13:17:17 UTC

Source terms

OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.