Malicious code in token-list-fetcher (npm)
The npm package 'token-list-fetcher' versions 1.0.0 and 1.0.1 contain malicious code that, upon loading, schedules a delayed HTTPS POST request sending the full environment variables and system user information to a hardcoded attacker-controlled endpoint. This exfiltration includes sensitive credentials such as npm tokens, GitHub tokens, AWS keys, and other secrets typically found in process.env in developer and CI environments. The package's advertised functionality is a cover, as the token-list-fetching feature is not implemented.
AI Analysis
Technical Summary
The 'token-list-fetcher' npm package versions 1.0.0 and 1.0.1 include malicious code that triggers a delayed beacon on module load. This beacon sends the entire process.env object, which often contains sensitive credentials, along with the hostname, username, and home directory information, to a hardcoded third-party URL (https://enjbyg3xk8l.x.pipedream.net/beacon). The rest of the package contains utility functions unrelated to the malicious behavior, serving as a cover for the exfiltration. This behavior poses a significant risk of credential leakage to attackers.
Potential Impact
Sensitive environment variables and system user information, including credentials such as npm tokens, GitHub tokens, and AWS keys, are exfiltrated to an attacker-controlled endpoint. This can lead to unauthorized access to developer accounts, cloud resources, and other systems relying on these secrets, potentially resulting in further compromise of infrastructure and data.
Mitigation Recommendations
No official patch or remediation is currently available for this malicious package. Users should immediately remove 'token-list-fetcher' versions 1.0.0 and 1.0.1 from their projects and dependency trees. Audit environments for potential credential exposure and rotate any secrets that may have been compromised. Avoid using untrusted or unknown npm packages and verify package authenticity before installation.
Malicious code in token-list-fetcher (npm)
Description
The npm package 'token-list-fetcher' versions 1.0.0 and 1.0.1 contain malicious code that, upon loading, schedules a delayed HTTPS POST request sending the full environment variables and system user information to a hardcoded attacker-controlled endpoint. This exfiltration includes sensitive credentials such as npm tokens, GitHub tokens, AWS keys, and other secrets typically found in process.env in developer and CI environments. The package's advertised functionality is a cover, as the token-list-fetching feature is not implemented.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The 'token-list-fetcher' npm package versions 1.0.0 and 1.0.1 include malicious code that triggers a delayed beacon on module load. This beacon sends the entire process.env object, which often contains sensitive credentials, along with the hostname, username, and home directory information, to a hardcoded third-party URL (https://enjbyg3xk8l.x.pipedream.net/beacon). The rest of the package contains utility functions unrelated to the malicious behavior, serving as a cover for the exfiltration. This behavior poses a significant risk of credential leakage to attackers.
Potential Impact
Sensitive environment variables and system user information, including credentials such as npm tokens, GitHub tokens, and AWS keys, are exfiltrated to an attacker-controlled endpoint. This can lead to unauthorized access to developer accounts, cloud resources, and other systems relying on these secrets, potentially resulting in further compromise of infrastructure and data.
Mitigation Recommendations
No official patch or remediation is currently available for this malicious package. Users should immediately remove 'token-list-fetcher' versions 1.0.0 and 1.0.1 from their projects and dependency trees. Audit environments for potential credential exposure and rotate any secrets that may have been compromised. Avoid using untrusted or unknown npm packages and verify package authenticity before installation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-12481
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a735741bf8831d539154e43
Added to database: 08/05/2026, 15:31:13 UTC
Last enriched: 08/05/2026, 17:01:02 UTC
Last updated: 08/05/2026, 17:01:02 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.