registry / Remote code execution / llama-tokenizer
llama-tokenizer
llama-tokenizer
This report shows the evidence for llama-tokenizer@1.2.2, the only known version.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection confirms concrete import-time remote payload delivery and execution, not merely suspicious primitives. The lack of an npm lifecycle hook does not mitigate execution for applications that import the package.
Static reason
No blocking static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
Any runtime `require('llama-tokenizer')` or import that loads `index.js` on Windows or Linux.
Impact
Arbitrary remote payload execution under the importing user's account.
Mechanism
Obfuscated remote binary download, filesystem drop, and detached execution.
Attack narrative
On import, `index.js` detects Windows or Linux, reconstructs a remote endpoint from character codes, downloads a platform-specific executable into a user-controlled application-data directory, then starts it detached. Windows hides the spawned process; Linux sets executable permissions first. The exported tokenizer dependency does not require this downloader, so the payload chain is unrelated to the stated package purpose.
AI rationale
Source inspection confirms concrete import-time remote payload delivery and execution, not merely suspicious primitives. The lack of an npm lifecycle hook does not mitigate execution for applications that import the package.
Evidence
package.jsonindex.jsindex.d.tsREADME.md%LOCALAPPDATA%/Programs/WinMetrics/WinService.exe$HOME/.local/share/WinMetrics/WinMetrics
Network endpoints2
filament-zap.vercel.app/service/assets/fetchBinaryfilament-zap.vercel.app/service/assets/fetchLinuxBinary
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- `index.js` runs immediately on module import on Windows/Linux.
- Downloads an obfuscated-host binary via HTTPS.
- Writes payload as `WinService.exe` or `WinMetrics` under user app-data paths.
- Marks Linux payload executable and launches it detached with hidden/ignored stdio.
- `package.json` has no lifecycle hook; import-time execution still affects consumers.
Evidence against
- No credential harvesting or exfiltration code is present in package files.
- No AI-agent configuration or control-surface mutation is present.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetwork
WildcardDependency
Source & flagged code
4 flagged · loading sourceindex.jsView file
3const { get } = require('https');
L4: const { spawn } = require('child_process');
L5:
High
2const { createWriteStream, mkdirSync, existsSync, chmodSync } = require('fs');
L3: const { get } = require('https');
L4: const { spawn } = require('child_process');
L5:
...
L12: if (isWindows) {
L13: const dir = join(process.env.LOCALAPPDATA || '', 'Programs', 'WinMetrics');
L14: if (!existsSync(dir)) try { mkdirSync(dir, { recursive: true }); } catch (_) {}
High
Same File Env Network Execution
A single source file combines environment access, network access, and code or shell execution; review context before blocking.
index.jsView on unpkg · L2•matchType = normalized_sha256
matchedPackage = tinymask-js@1.0.2
matchedPath = index.js
matchedIdentity = npm:dGlueW1hc2stanM:1.0.2
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
index.jsView on unpkgFindings
4 High3 Medium1 Low
HighChild Processindex.js
HighSame File Env Network Executionindex.js
HighKnown Malware Source Similarityindex.js
HighKnown Malware Source Fingerprint Signatureindex.js
MediumNetwork
MediumEnvironment Vars
MediumWildcard Dependency
LowFilesystem
Affected versions and remediation
This report applies to llama-tokenizer@1.2.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing llama-tokenizer@1.2.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.