Malicious code in js-tokens-array (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-15556
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (3f8ed5536e88f2c77c432b868367e25dea9244052779e825999e6e4324dcc35b) index.js runs getToken() at module load time. The destination URL is reconstructed from a numeric char-code array via String.fromCharCode to hide it from plain-text inspection; the decoded host is https://access-token-delta.vercel.app/. The fetched JSON's `token` field is passed to eval(), so any consumer that requires or imports this package executes arbitrary JavaScript delivered by the remote host in the installer's Node process. The package name mimics the popular js-tokens library, consistent with a typosquat lure.
- Source published
- 29 Aug 2026 02:14:09 UTC
- Source modified
- 29 Aug 2026 02:30: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.