Malicious Code in djstream (npm)

djstream Updated 02 Oct 2025

Summary

07/11/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8478: Malicious code in djstream (npm). Affects djstream versions 1.0.0. 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

djstream is an npm package that provides functionality for streaming audio and video content. It is commonly used in web applications to handle media streaming. This package is vulnerable to a malicious code injection attack, which can compromise the security of any system where it is installed or running.

Vulnerability Detail

The vulnerability in djstream is due to the presence of malicious code in the package. This code can give full control of the affected computer to an external entity, potentially leading to unauthorized access and data breaches. Any secrets and keys stored on the compromised computer should be rotated immediately from a different computer. Simply removing the package may not be sufficient to remove all the malicious software installed as a result of this vulnerability.

How To Fix

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

npm uninstall djstream

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

There is no known workaround for this vulnerability. It is crucial to follow the steps mentioned in the 'how_to_fix' section to mitigate the risk and ensure the security of the system.

Conclusion

The presence of malicious code in djstream poses a significant security risk to any system where it is installed or running. It is crucial to take immediate action to mitigate this vulnerability, including rotating secrets and keys, removing the package, and conducting a thorough security audit. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for djstream →

Share this vulnerability

FAQ

djstream is an npm package used for streaming audio and video content in web applications.

The presence of malicious code in djstream can compromise the security of your system, potentially leading to unauthorized access and data breaches.

If you have djstream installed, it is recommended to rotate all secrets and keys stored on the affected computer from a different, secure computer. Remove the djstream package and perform a thorough security audit.

Removing the djstream package may not be sufficient to remove all the malicious software installed as a result of this vulnerability. It is important to follow the recommended steps for remediation.

It is advisable to implement a robust monitoring system that can detect and alert you about any suspicious activities or signs of compromise on your system.

How To Fix

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

npm uninstall djstream

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