Critical Malicious Code Vulnerability in vanilla-cacher Package

vanilla-cacher Updated 02 Oct 2025

Summary

30/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6375: Malicious code in vanilla-cacher (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The vanilla-cacher package is an npm module designed for caching functionality in JavaScript applications. It allows developers to store and retrieve data efficiently, enhancing application performance. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on, making it a significant risk for developers and users alike.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the vanilla-cacher package. This code can lead to full compromise of any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code poses severe risks, including data theft and system manipulation, as it may grant external entities control over the affected systems.

How To Fix

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

npm uninstall vanilla-cacher

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

Currently, the only effective workaround is to uninstall the vanilla-cacher package. You can do this by running the following command in your terminal: npm uninstall vanilla-cacher. Additionally, consider using alternative caching solutions that do not have known vulnerabilities.

Conclusion

The discovery of malicious code in the vanilla-cacher package poses a serious threat to users and developers. Immediate action is required to uninstall the package and secure any compromised systems. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for vanilla-cacher →

Share this vulnerability

FAQ

The malicious code is designed to compromise the security of the system, potentially allowing unauthorized access to sensitive information.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.

Immediately uninstall the package using npm uninstall vanilla-cacher and rotate any secrets or keys stored on the affected system.

Yes, consider using other caching libraries that are well-reviewed and have no known vulnerabilities.

While removing the package is essential, there is no guarantee that all malicious software has been removed. It's advisable to conduct a thorough security audit of the system.

How To Fix

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

npm uninstall vanilla-cacher

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