Malicious Code Detected in bunker-cache Package

bunker-cache Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16346: Malicious code in bunker-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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The bunker-cache package is an npm library designed for caching purposes, allowing developers to store and retrieve data efficiently. It is commonly used in various Node.js applications to enhance performance by reducing the need for repeated data fetching. However, this package has been found to contain malicious code, posing a significant security risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the bunker-cache package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate the risks associated with this vulnerability.

How To Fix

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

npm uninstall bunker-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 temporary workaround, consider removing the bunker-cache package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall bunker-cache'. This will prevent any potential exploitation of the vulnerability while you await a fix.

Conclusion

The discovery of malicious code in the bunker-cache package highlights the importance of regularly monitoring and updating open-source dependencies. Users must take immediate action to protect their applications by updating or removing the affected package. Utilizing tools like Vulert can help in identifying vulnerabilities in real-time.

See every vulnerability recorded for bunker-cache →

Share this vulnerability

FAQ

bunker-cache is an npm package used for caching data in Node.js applications, enhancing performance by reducing data fetching.

The malicious code can lead to unauthorized access and data breaches, posing significant security risks to applications using the package.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

As of now, a patched version has not been released. Users are advised to monitor the package repository for updates.

If you cannot update the package, consider uninstalling it temporarily to mitigate the risk until a secure version is available.

How To Fix

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

npm uninstall bunker-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