Malicious code in token-list-fetcher (npm)
Historical advisory saved 24 Oct 2026 13:17:17 UTC. The publisher may have updated it since then. Latest advisory.
osv · MAL-2026-12481
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (e0c4aa27fc6318b8e3b7e2ec6718d3254147df0032799c5667dd8e88a24ca188) 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.
- Source published
- 5 Aug 2026 13:04:37 UTC
- Source modified
- 5 Aug 2026 13:36:18 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.