Malicious Code Detected in export-double-cache-benchmark-resolve Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20063: Malicious code in export-double-cache-benchmark-resolve (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 export-double-cache-benchmark-resolve package is an npm library designed for benchmarking cache resolutions. It is commonly used in applications that require performance testing of caching mechanisms. However, this package has been identified to contain malicious code, posing a significant risk to users who integrate it into their projects.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the export-double-cache-benchmark-resolve package. This code can potentially compromise the security of applications that utilize this package, leading to unauthorized access, data breaches, or other harmful effects. The issue was reported by Amazon Inspector, highlighting the need for immediate attention from developers using this package.

How To Fix

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

npm uninstall export-double-cache-benchmark-resolve

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, you can avoid using the export-double-cache-benchmark-resolve package until a secure version is released. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the export-double-cache-benchmark-resolve package underscores the importance of vigilance in managing open-source dependencies. Developers are encouraged to remove the affected package and utilize tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for export-double-cache-benchmark-resolve →

Share this vulnerability

FAQ

The malicious code can compromise application security, potentially leading to unauthorized access or data breaches.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected.

Immediately remove the export-double-cache-benchmark-resolve package from your project and monitor for any updates or patches.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.

Using packages with known vulnerabilities can expose your application to security risks, including data breaches and unauthorized access.

How To Fix

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

npm uninstall export-double-cache-benchmark-resolve

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