Advisory

MAL-2026-13351

Also known as: None

Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.

Summary

Malicious code in spl-token-utils (npm)

Details

---
_-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (f95b625c92e85b1c0d5c10a192c70f8f82cf8d3b2ac7b66c034635b680785654)
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.

Severity

Not rated by the source.

Dates

Published
2026-08-05 15:39 UTC
Modified
2026-08-05 16:51 UTC

Affected packages and fixes

spl-token-utils

npm · All systems

Affected

  • Versions: 1.4.2

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: OpenSSF Malicious Packages · Apache-2.0

Sources & licences