If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (985d4d8e5069084334daa08512249314d36d9fa8662adef050021c2400dacbdd)
@zzzgenesis00/solana-spl-token@0.4.0 impersonates the Solana SPL Token package and runs postinstall.js on `npm install`. The script harvests host identity, reads ~/.ssh, ~/.npmrc, and ~/.gitconfig, probes Chrome/Firefox profiles and cryptocurrency wallet directories, and scrapes ~40 credential-shaped environment variables including NPM_TOKEN, NODE_AUTH_TOKEN, GITHUB_TOKEN, AWS_*, MNEMONIC, SEED_PHRASE, SOLANA_PRIVATE_KEY, and Helius/Infura/Alchemy API keys. It shells out via child_process.execSync to run `npm whoami` and `git config --global user.email`, capturing the installer's npm login identity alongside the stolen ~/.npmrc auth token. The collected JSON is exfiltrated over two channels: the Telegram Bot API (hardcoded bot token, chat_id) at api.telegram.org, and an HTTP POST to 40f955f39128bd79-178-249-214-24.serveousercontent.com/collect (a serveo tunnel). Execution is delayed with setTimeout and random jitter to obscure the beacon.