Critical Malicious Code Vulnerability in llmstash Package

llmstash Updated 20 Mar 2026

Summary

20/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1956: Malicious code in llmstash (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

llmstash is an npm package designed for managing and storing data in a lightweight manner. It is commonly used in JavaScript applications for its simplicity and efficiency. However, the package has been identified to contain malicious code, posing significant security risks to any system that has it installed.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the llmstash package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to malicious actors who have manipulated the package to gain control over affected systems. Users are advised to treat any system running this package as fully compromised.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall llmstash

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There are no effective workarounds for this vulnerability other than removing the package and securing the system. Users should ensure that all sensitive data is rotated and monitored for any unauthorized access.

Conclusion

The llmstash package has been identified as containing malicious code that can compromise systems. Immediate removal and rotation of sensitive data are necessary to mitigate risks. Users are encouraged to utilize tools like Vulert for ongoing monitoring of their dependencies.

See every vulnerability recorded for llmstash →

Share this vulnerability

FAQ

Immediately remove the llmstash package from your system and rotate any secrets or keys that may have been compromised.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and complete system compromise.

Yes, Vulert provides real-time monitoring and alerts for open-source vulnerabilities using just your package-lock.json file.

While most npm packages are safe, it is essential to regularly monitor and audit your dependencies for vulnerabilities and only use trusted sources.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall llmstash

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback