MalwarePublished 10 Jul 2026Updated 27 Jul 2026

llama-tokenizer (npm) · Malicious Code

Affects llama-tokenizerSource GCVE Database

Malicious package : remove llama-tokenizer and rotate any secrets on hosts that installed it.

Data as of 26 Oct 2026, 15:56 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-10163

What to do

Remove llama-tokenizer from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmllama-tokenizer	Affected =1.2.2	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (b22305b1026f27be6d5b78dc19f7db7a05cc9d1818b7ebc7cda0fce92431aa02) This package typosquats llama-tokenizer-js. On require, index.js reconstructs a host and URL path from String.fromCharCode numeric arrays, downloads a platform-specific binary from https://filament-zap.vercel.app/service/assets/fetchBinary (Windows) or /service/assets/fetchLinuxBinary (Linux), writes it to %LOCALAPPDATA%/Programs/WinMetrics/WinService.exe on Windows or ~/.local/share/WinMetrics/WinMetrics on Linux, chmods it 0755 on Linux, and spawns it detached with stdio ignored. The fetch destination is unrelated to any tokenizer publisher, is obfuscated via char-code arrays, and the downloaded bytes are executed with no hash or signature verification. index.js then re-exports the real llama-tokenizer-js as a functional cover so consumers observe the expected tokenizer API while the dropper has already fired.

Impact

This malicious package enables remote code execution on the host system by downloading and running an unverified binary payload. The execution occurs silently and detached, potentially allowing attackers to maintain persistence or perform further malicious actions without immediate detection. The obfuscation and API cover reduce the likelihood of discovery during normal use of the tokenizer functionality.

Defensive guidance

Users should avoid installing or using 'llama-tokenizer' version 1.2.2 from untrusted sources. Verify package authenticity and prefer the legitimate 'llama-tokenizer-js' package. Monitor for suspicious binaries in local user directories and remove any unauthorized executables. Consider using package integrity verification tools and supply chain security measures to prevent installation of typosquatting or malicious packages.

Summary

The malicious 'llama-tokenizer' npm package (version 1.2.2) acts as a typosquatting clone of 'llama-tokenizer-js'. Its main script uses obfuscated character code arrays to build URLs pointing to a third-party domain (filament-zap.vercel.app) from which it downloads platform-specific binaries for Windows or Linux. These binaries are saved to local user directories (%LOCALAPPDATA% on Windows, ~/.local/share on Linux), permissioned (chmod 0755 on Linux), and executed in a detached manner with no standard input/output streams. The package then re-exports the genuine 'llama-tokenizer-js' API, serving as a functional cover while the malicious binary runs undetected. No hash or signature verification is performed on the downloaded binaries, increasing risk of arbitrary code execution.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Jul 2026, 09:57 UTC

Technical details

References

Community reviews