Which versions of js-tokens-array are malicious?

The following npm versions of js-tokens-array are flagged malicious: 1.0.0, 1.1.1. Treat any of these as compromised.

How do I remediate js-tokens-array if I installed it?

js-tokens-array is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed js-tokens-array — how do I know if it already compromised me?

If js-tokens-array was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is js-tokens-array part of a known attack campaign?

Yes — js-tokens-array is associated with the IN-MAL-2026-019143, IN-MAL-2026-019141 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find js-tokens-array across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for js-tokens-array (2 malicious versions).

Malicious package

js-tokens-arraynpm

Advisory published Aug 29, 2026Updated Aug 29, 2026

js-tokens-array is a confirmed malicious npm package (MAL-2026-15556) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in js-tokens-array (npm)

MAL-2026-15556

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall js-tokens-array

What this malware does

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.

Malicious versions

2 flagged

1.0.01.1.1

Indicators of compromise (SHA-256)

35bd7f6a22d21fe244f3564f2b9fdd874a7824637fc6cc2d9726b2eeb9b88e4f

3f8ed5536e88f2c77c432b868367e25dea9244052779e825999e6e4324dcc35b

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for js-tokens-array (2 malicious versions).
If you installed it — respond
js-tokens-array is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If js-tokens-array was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. js-tokens-array on npm has been identified as a malicious package (versions 1.0.0, 1.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019143IN-MAL-2026-019141

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks js-tokens-array-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database