Which versions of token-list-fetcher are malicious?

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

How do I remediate token-list-fetcher if I installed it?

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

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

Yes — token-list-fetcher is associated with the IN-MAL-2026-014872, IN-MAL-2026-014879 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 token-list-fetcher 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 token-list-fetcher (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging token-list-fetcher across your stack and pipelines.

Malicious package

token-list-fetchernpm

token-list-fetcher is a confirmed malicious npm package (MAL-2026-12481) 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 token-list-fetcher (npm)

MAL-2026-12481

Immediate action

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

npm uninstall token-list-fetcher

What this malware does

On require, index.js schedules a delayed HTTPS POST that transmits the full process.env object along with os.hostname(), os.userInfo().username, and os.homedir() to the hardcoded third-party endpoint https://enjbyg3xk8l.x.pipedream.net/beacon. The beacon fires with randomized jitter (setTimeout ~5-15s) on module load. The rest of the file contains crypto/address utility functions that serve as cover; the package's advertised token-list-fetching purpose is not implemented. process.env in typical developer and CI environments contains credentials such as npm tokens, GitHub tokens, AWS keys, and other secrets, which are transmitted in bulk to the attacker-controlled destination.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

8b42910ab431aaf546eff412062b5dddcfe4053c305b5ad2a2cfa8b0b8ca0dfe

e0c4aa27fc6318b8e3b7e2ec6718d3254147df0032799c5667dd8e88a24ca188

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 token-list-fetcher (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging token-list-fetcher across your stack and pipelines.
If you installed it — respond
token-list-fetcher 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 token-list-fetcher 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 token-list-fetcher 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. token-list-fetcher 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-014872IN-MAL-2026-014879

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks token-list-fetcher-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