Critical Malicious Code Vulnerability in zuper-stream Package

zuper-stream Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190862: Malicious code in zuper-stream (npm). Affects zuper-stream versions 2.0.9. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The zuper-stream package is a Node.js library designed for streaming data efficiently in various applications. It is widely used in the npm ecosystem for its performance and ease of integration. However, recent findings have revealed that this package contains malicious code, posing significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the zuper-stream package, identified as version 2.0.9. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to a malicious actor who has exploited the npm ecosystem to distribute harmful software. The ramifications of this vulnerability are severe, as it can lead to complete system compromise and data breaches.

How To Fix

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

npm uninstall zuper-stream

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, there are no effective workarounds for this vulnerability other than removing the package entirely. Users should also monitor their systems for any signs of compromise.

Conclusion

The discovery of malicious code in the zuper-stream package poses a critical threat to users. Immediate action is required to remove the package and secure any sensitive information. Continuous monitoring with tools like Vulert can help prevent future vulnerabilities.

See every vulnerability recorded for zuper-stream →

Share this vulnerability

FAQ

zuper-stream is a Node.js library used for efficient data streaming in applications.

If you have the zuper-stream package version 2.0.9 installed, your system is at risk. You can check your package-lock.json file or use Vulert to monitor vulnerabilities.

Immediately rotate all secrets and keys from a different, secure computer to prevent unauthorized access.

No, there is currently no patched version of the zuper-stream package. The only action is to uninstall it.

Vulert monitors your package-lock.json file for vulnerabilities in real-time, alerting you to any issues without needing access to your code.

How To Fix

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

npm uninstall zuper-stream

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