Malicious code in common-array-token (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-15550
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (bf8dc846e743e9517d8444feb25299ce05d9c6e060a050fdaa1b3b44a8cb5cbd) package.json declares scripts.postinstall = 'node index.js'. On npm install, index.js reconstructs a URL from a String.fromCharCode numeric array (decoding to https://access-token-delta.vercel.app/), fetches JSON from that endpoint, and passes the returned 'token' field to eval(). Any JavaScript served by that endpoint executes on the installer's machine with the user's privileges at install time. The endpoint is hardcoded and controlled by the package author; the char-code obfuscation conceals the destination from plaintext scanning. There is no legitimate purpose served by fetching and eval'ing remote code from an obfuscated URL in a postinstall hook.
- Source published
- 29 Aug 2026 02:14:47 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.