Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@wethenorth12/solana-spl-tokennpm

@wethenorth12/solana-spl-token is a confirmed malicious npm package (MAL-2026-12100) 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 @wethenorth12/solana-spl-token (npm)

MAL-2026-12100
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @wethenorth12/solana-spl-token

What this malware does

@wethenorth12/solana-spl-token is a typosquat of the legitimate @solana/spl-token package. On module load, index.js collects hostname, username, home directory, platform, current working directory, and the entire process.env, base64-encodes the JSON payload, and sends it via HTTPS GET to a hardcoded Telegram Bot API endpoint (bot id 7231970337, chat_id 8969499041). A flag file in the OS tmpdir prevents re-sending on subsequent requires. The package additionally ships stub wallet primitives (createWallet, generateMnemonic, signTransaction) that return random or no-op values when the real @solana/spl-token is not present, while marketing itself in the README as a drop-in replacement. Environment variables in CI and developer machines routinely contain credentials such as AWS_*, GITHUB_TOKEN, NPM_TOKEN, and database connection strings, all of which leave the installer's host to an author-controlled Telegram destination on any require of this package.

Malicious versions

1 flagged
0.4.0

Indicators of compromise (SHA-256)

7dde46db2fbc17fae2957070f85bc43fdb1d265444f2e5adc936faa6f82e96e2

Detection & response playbook

Credential / info stealer

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @wethenorth12/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 @wethenorth12/solana-spl-token across your stack and pipelines.

  2. If you installed it — respond

    @wethenorth12/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.

  3. Did it already run?

    If @wethenorth12/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.

  4. How O3 protects you

    O3 blocks @wethenorth12/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. @wethenorth12/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-013444

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @wethenorth12/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
@wethenorth12/solana-spl-token (npm) malicious package — MAL-2026-12100 | O3 Security