NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Part of a larger attack: @wethenorth12 published 23 malicious packages. See the full campaign →
Malicious package

@wethenorth12/spl-token-utilsnpm

Advisory published Updated

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

Malicious code in @wethenorth12/spl-token-utils (npm)

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

What this malware does

@wethenorth12/spl-token-utils advertises itself as a drop-in replacement for @solana/spl-token. On require(), index.js serializes the full process.env together with hostname, username, homedir, platform, cwd, and a timestamp, base64-encodes the JSON, and sends it via HTTPS GET to api.telegram.org bot 7231970337 chat_id 8969499041. A sentinel file in the temp directory suppresses repeat sends. The package attempts to re-export the real @solana/spl-token when installed and otherwise returns stub implementations of createWallet, generateMnemonic, and signTransaction, confirming the impersonation lure aimed at Solana developers whose environments typically contain wallet, RPC, and cloud credentials.

Malicious versions

1 flagged
1.4.2

Indicators of compromise (SHA-256)

7d7f9cee39cc030c866ec58a0744ef387333cf5578a35f4b10aa211c19c61b7b

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @wethenorth12/spl-token-utils (version 1.4.2).

  2. If you installed it — respond

    @wethenorth12/spl-token-utils 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/spl-token-utils was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-013442

References

Credits

  • Amazon Inspector · finder

Detect & block this

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