Malicious code in tizen-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-13966
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (cf90f542c0f81ff50f903a216f44a5870bc0ac5ede472fa2c41af447994b58e4) On npm install, the package's postinstall lifecycle script collects host identifiers (os.hostname(), process.platform, process.arch, Node.js version, package name, and npm lifecycle event) and POSTs them as JSON over HTTPS to the hardcoded endpoint https://8kq1s58l.instances.poc.jchunt.top/tizen-webdriver-cli, with a 3-second timeout and errors silently swallowed. The behavior runs unconditionally at install time with no opt-in, no disclosure in normal install output, and no first-party relationship between the destination host and the package's advertised purpose (a Tizen WebDriver CLI, resembling shaka-project's generic-webdriver-server Tizen backend). The package name suggests dependency-confusion targeting of that legitimate project.
- Source published
- 13 Aug 2026 20:45:24 UTC
- Source modified
- 13 Aug 2026 21:00:11 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.