Which versions of @wethenorth12/spl-token-utils are malicious?

The following npm versions of @wethenorth12/spl-token-utils are flagged malicious: 1.4.2. Treat any of these as compromised.

How do I remediate @wethenorth12/spl-token-utils if I installed it?

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

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

If @wethenorth12/spl-token-utils 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 @wethenorth12/spl-token-utils part of a known attack campaign?

Yes — @wethenorth12/spl-token-utils is associated with the IN-MAL-2026-013442 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 @wethenorth12/spl-token-utils 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 @wethenorth12/spl-token-utils (version 1.4.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @wethenorth12/spl-token-utils across your stack and pipelines.

Malicious package

@wethenorth12/spl-token-utilsnpm

@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

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @wethenorth12/spl-token-utils (version 1.4.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @wethenorth12/spl-token-utils across your stack and pipelines.
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.
Did it already run?
If @wethenorth12/spl-token-utils 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 @wethenorth12/spl-token-utils 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/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

npmjs.com

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