Critical Malicious Code Vulnerability in @polystream/streaming Package

@polystream/streaming Updated 31 Dec 2025

Summary

31/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-193009: Malicious code in @polystream/streaming (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 @polystream/streaming package is a Node.js library designed for streaming applications, providing functionalities that facilitate real-time data transmission and processing. However, it has been identified as containing malicious code that compromises the security of any system where it is installed, making it a significant risk for developers and organizations relying on this package.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the @polystream/streaming package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it could lead to data breaches and loss of control over the affected systems. The malicious nature of the code has been confirmed by security researchers, categorizing it under CWE-506, which pertains to products containing malicious code.

How To Fix

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

npm uninstall @polystream/streaming

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 to mitigate the risks associated with the malicious code in the @polystream/streaming package. The only recommended action is to uninstall the package and secure your system.

Conclusion

The @polystream/streaming package has been identified as containing malicious code that poses a significant risk to any system where it is installed. Immediate action is required to remove the package and secure sensitive information. Regular monitoring for vulnerabilities is essential to maintain the security of your applications.

See every vulnerability recorded for @polystream/streaming →

Share this vulnerability

FAQ

It is a Node.js library used for streaming applications, enabling real-time data transmission and processing.

The malicious code can fully compromise your system, allowing unauthorized access to sensitive information and control over your computer.

You should immediately uninstall the package and rotate any secrets or keys stored on the affected system.

No, there is currently no patched version available for the @polystream/streaming package.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

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

npm uninstall @polystream/streaming

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