Malicious Code Detected in cache-buffer-relay-troposphere Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16418: Malicious code in cache-buffer-relay-troposphere (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 cache-buffer-relay-troposphere package is an npm library designed to facilitate the management of cache buffers in applications. It is utilized for its efficiency in handling data streams and optimizing performance. However, it has been identified to contain malicious code, posing significant risks to applications that depend on it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the cache-buffer-relay-troposphere package. This code can lead to unauthorized access, data breaches, or other malicious activities within applications that utilize this package. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall cache-buffer-relay-troposphere

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 using alternative packages that provide similar functionality without the associated risks. Always ensure to review the security status of any package before integrating it into your application.

Conclusion

The cache-buffer-relay-troposphere package has been found to contain malicious code, posing serious risks to applications that utilize it. Immediate action is required to remove or replace this package to safeguard your application from potential threats.

See every vulnerability recorded for cache-buffer-relay-troposphere →

Share this vulnerability

FAQ

It is an npm library used for managing cache buffers in applications, optimizing data stream handling.

The malicious code was identified through security assessments conducted by Amazon Inspector.

Using this package can lead to unauthorized access, data breaches, and other security vulnerabilities in your application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner without any signup.

If immediate removal is not possible, consider implementing strict access controls and monitoring to mitigate potential risks until you can update or replace the package.

How To Fix

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

npm uninstall cache-buffer-relay-troposphere

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