@zzzcrypto/solana-spl-token
Affected
- Versions:
0.4.0
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 @zzzcrypto/solana-spl-token (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (6ceac45508e2f9506a082b2195d3bae4b046f096d11856d72ea53f784ad5992e)
@zzzcrypto/[email protected] is a typosquat/impersonation of @solana/spl-token (README self-describes as a 'drop-in replacement'; author metadata is set to 'solana-labs'). On module load, index.js enumerates the full process.env and augments it with hostname, username, homedir, platform, and cwd, base64-encodes the JSON payload, and sends it as an HTTPS GET to api.telegram.org/bot<redacted>/sendMessage with chat_id=8969499041. A temporary flag file gates the beacon to once per host. Variable names are randomized (dmcp, uqxj, bhhs, _h, _flag) and the payload is base64-wrapped to hide the exfil body. If the real @solana/spl-token is not installed, the package falls back to a stub API exporting createWallet/generateMnemonic that returns random bytes rather than real key material. On typical developer and CI machines, process.env contains credentials such as AWS_*, GITHUB_TOKEN, and NPM_TOKEN, which are shipped off-host to the attacker's Telegram chat.
Not rated by the source.
0.4.0None 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