Malicious Code Detected in dslive Package - Immediate Action Required

dslive Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18941: Malicious code in dslive (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The dslive package is an npm library designed for real-time data streaming and visualization. It is widely used in applications that require dynamic data updates and user interactions. However, the package has been found to contain malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the dslive package originates from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code can lead to unauthorized access, data breaches, and potential exploitation of user systems. The malicious nature of the code means that it can execute harmful actions without the user's consent, making it critical to address this issue promptly.

How To Fix

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

npm uninstall dslive

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 removing the dslive package from your project until a secure version is released. You can uninstall it using the following command: npm uninstall dslive.

Conclusion

The discovery of malicious code in the dslive package highlights the importance of maintaining secure dependencies in software projects. Immediate action is required to update or remove the affected package to protect applications from potential threats.

See every vulnerability recorded for dslive →

Share this vulnerability

FAQ

The dslive package is used for real-time data streaming and visualization in web applications.

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

If you cannot update the package, consider removing it from your project as a temporary measure to mitigate risks.

Detailed information about the vulnerability can be found on the GitHub repository of the malicious packages project.

Yes, tools like Vulert can help you monitor your dependencies for vulnerabilities using just the package-lock.json file.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall dslive

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