Which versions of commonjs-code-token are malicious?

The following npm versions of commonjs-code-token are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate commonjs-code-token if I installed it?

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

If commonjs-code-token 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 commonjs-code-token part of a known attack campaign?

Yes — commonjs-code-token is associated with the IN-MAL-2026-018754, IN-MAL-2026-018753 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 commonjs-code-token across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for commonjs-code-token (2 malicious versions).

Malicious package

commonjs-code-tokennpm

Advisory published Aug 26, 2026Updated Aug 26, 2026

commonjs-code-token is a confirmed malicious npm package (MAL-2026-14534) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in commonjs-code-token (npm)

MAL-2026-14534

Immediate action

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

npm uninstall commonjs-code-token

What this malware does

On npm install, the package's postinstall hook runs index.js, which fetches JSON from https://access-token-delta.vercel.app and passes the returned token field directly to eval(). Whoever controls that endpoint obtains arbitrary code execution on the installing machine, and the fetched content is mutable at any time. The package advertises itself with a README for an unrelated multithreaded cache library (node-cache-multithread) while the actual package identity is commonjs-code-token, a metadata/behavior mismatch consistent with a cover story. No legitimate functionality is shipped in the package.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

b5f30d280304d5e3e2f52c01495981c888bc161d54342821c90944ee908798d5

c6ab469a55ec3f0650bc2185b91e884304cf1e370b1e17992a328479ce4883ad

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for commonjs-code-token (2 malicious versions).
If you installed it — respond
commonjs-code-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 commonjs-code-token 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. commonjs-code-token on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018754IN-MAL-2026-018753

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks commonjs-code-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