Which versions of spl-token-utils are malicious?

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

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

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 spl-token-utils — how do I know if it already compromised me?

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

Yes — spl-token-utils is associated with the IN-MAL-2026-015780 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 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 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 spl-token-utils across your stack and pipelines.

Malicious package

spl-token-utilsnpm

spl-token-utils is a confirmed malicious npm package (MAL-2026-13351) 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 spl-token-utils (npm)

MAL-2026-13351

Immediate action

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

npm uninstall spl-token-utils

What this malware does

On require, index.js serializes the full process.env together with hostname, username, homedir, platform, cwd, and package metadata, base64-encodes the payload, and sends it via an HTTPS GET to api.telegram.org/bot<redacted>/sendMessage with a hardcoded chat_id (8969499041). A marker file in the OS tmpdir suppresses repeat sends. The package presents itself as a drop-in replacement for @solana/spl-token and attempts to require and re-export the real @solana/spl-token so consumers see functional behavior while the exfiltration has already fired. Bulk process.env harvest at import time captures whatever credentials the installer's Node process has in environment — cloud keys, CI/publish tokens, database URLs — none of which relate to any legitimate SPL/Solana utility function. The typosquat name (spl-token-utils vs @solana/spl-token) makes accidental installs likely.

Malicious versions

1 flagged

1.4.2

Indicators of compromise (SHA-256)

f95b625c92e85b1c0d5c10a192c70f8f82cf8d3b2ac7b66c034635b680785654

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 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 spl-token-utils across your stack and pipelines.
If you installed it — respond
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 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 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. 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-015780

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks 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