Malicious code in chromecast-webdriver-cli (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-14231
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (0c858cd5357d77c39366f7bd1cc1985a5d7012d33da45d6dc9667544b54198d6) [email protected] runs a postinstall lifecycle script that collects host metadata (os.hostname(), platform, arch, node version, package name, npm lifecycle event) and POSTs it as JSON to the hardcoded host h77svwt7.instances.poc.jchunt.top at /chromecast-webdriver-cli on every `npm install`. The destination is an anonymous subdomain unrelated to the upstream project the package name references (shaka-project/generic-webdriver-server). No opt-in, no first-party publisher relationship, and no functional package code — the beacon fires automatically and transmits installer-identifying data to a third-party endpoint. The package name reproduces a legitimate-sounding upstream tool, which is the fingerprint of a dependency-confusion / typosquat beacon.
- Source published
- 19 Aug 2026 03:41:37 UTC
- Source modified
- 19 Aug 2026 04:00:18 UTC
- Saved 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
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.