supply chain event / NVI-00019036 / Revision 1
Malicious code in js-tokens-array (npm)
GitHub lists this malware advisory for js-tokens-array, js-tokens-array. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
js-tokens-array
source listed= 1.0.0
## 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. --- Credit: OpenSSF (source)
js-tokens-array
source listed= 1.1.1
## 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. --- Credit: OpenSSF (source)
03 / Response
What to do next
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-8crw-r25r-mwv4 ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.