@wethenorth12/spl-token-utils
This report shows the evidence for @wethenorth12/spl-token-utils@1.4.2, the only known version.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-12103 confirms this npm version as malicious.
Advisory
MAL-2026-12103
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @wethenorth12/spl-token-utils (npm)
Details
@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.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to @wethenorth12/spl-token-utils@1.4.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing @wethenorth12/spl-token-utils@1.4.2. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.