token-list-fetcher
Affected
- Versions:
1.0.0,1.0.1
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in token-list-fetcher (npm)
---
_-= 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.
Not rated by the source.
1.0.0, 1.0.1None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0