Which versions of @zzzgenesis00/solana-spl-token are malicious?

The following npm versions of @zzzgenesis00/solana-spl-token are flagged malicious: 0.4.0. Treat any of these as compromised.

How do I remediate @zzzgenesis00/solana-spl-token if I installed it?

@zzzgenesis00/solana-spl-token is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @zzzgenesis00/solana-spl-token — how do I know if it already compromised me?

If @zzzgenesis00/solana-spl-token was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @zzzgenesis00/solana-spl-token part of a known attack campaign?

Yes — @zzzgenesis00/solana-spl-token is associated with the IN-MAL-2026-014390 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @zzzgenesis00/solana-spl-token across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @zzzgenesis00/solana-spl-token (version 0.4.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @zzzgenesis00/solana-spl-token across your stack and pipelines.

Malicious package

@zzzgenesis00/solana-spl-tokennpm

@zzzgenesis00/solana-spl-token is a confirmed malicious npm package (MAL-2026-12123) that steals credentials and exfiltrates sensitive data (malicious version 0.4.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @zzzgenesis00/solana-spl-token (npm)

MAL-2026-12123

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @zzzgenesis00/solana-spl-token

What this malware does

@zzzgenesis00/[email protected] 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.

Malicious versions

1 flagged

0.4.0

Indicators of compromise (SHA-256)

985d4d8e5069084334daa08512249314d36d9fa8662adef050021c2400dacbdd

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @zzzgenesis00/solana-spl-token (version 0.4.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @zzzgenesis00/solana-spl-token across your stack and pipelines.
If you installed it — respond
@zzzgenesis00/solana-spl-token is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @zzzgenesis00/solana-spl-token was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @zzzgenesis00/solana-spl-token before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @zzzgenesis00/solana-spl-token on npm has been identified as a malicious package (version 0.4.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014390

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @zzzgenesis00/solana-spl-token-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database