Which versions of common-array-token are malicious?

The following npm versions of common-array-token are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate common-array-token if I installed it?

common-array-token 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 common-array-token — how do I know if it already compromised me?

If common-array-token was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is common-array-token part of a known attack campaign?

Yes — common-array-token is associated with the IN-MAL-2026-019145 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 common-array-token across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for common-array-token (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging common-array-token across your stack and pipelines.

Malicious package

common-array-tokennpm

common-array-token is a confirmed malicious npm package (MAL-2026-15550) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in common-array-token (npm)

MAL-2026-15550

Immediate action

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

npm uninstall common-array-token

What this malware does

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

bf8dc846e743e9517d8444feb25299ce05d9c6e060a050fdaa1b3b44a8cb5cbd

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for common-array-token (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging common-array-token across your stack and pipelines.
If you installed it — respond
common-array-token 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 common-array-token was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks common-array-token before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

IN-MAL-2026-019145

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks common-array-token-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