Malicious Code Detected in cache-emulate-fire-encrypt-cache Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16420: Malicious code in cache-emulate-fire-encrypt-cache (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The cache-emulate-fire-encrypt-cache package is an npm library designed for caching and encryption functionalities. It is utilized by developers to enhance data security and improve application performance. However, this package has been found to contain malicious code, posing significant risks to applications that rely on it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the cache-emulate-fire-encrypt-cache package. This code can potentially compromise the security of applications using the package, leading to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions.

How To Fix

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

npm uninstall cache-emulate-fire-encrypt-cache

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

As a workaround, consider using alternative packages that provide similar caching and encryption functionalities without the associated risks. Always review the security status of any package before integrating it into your project.

Conclusion

The cache-emulate-fire-encrypt-cache package has been identified as containing malicious code, which poses significant risks to applications using it. It is crucial to remove the package and consider alternatives to ensure the security of your application.

See every vulnerability recorded for cache-emulate-fire-encrypt-cache →

Share this vulnerability

FAQ

It is an npm library used for caching and encryption, aimed at improving data security in applications.

The specific nature of the malicious code has not been disclosed, but it poses risks such as unauthorized access and data breaches.

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

Consider using alternative packages that provide similar functionalities, and ensure to monitor your application for any unusual behavior.

Regularly check for updates to your packages and utilize tools like Vulert to monitor vulnerabilities in real-time.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall cache-emulate-fire-encrypt-cache

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