Malicious Code Detected in dspmgr Package: Immediate Action Required

dspmgr Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18944: Malicious code in dspmgr (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 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 dspmgr package is an npm library designed for managing digital signal processing tasks. It provides various functionalities that facilitate the manipulation and analysis of signals in software applications. However, recent findings have revealed that this package contains malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the dspmgr package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other harmful actions that can affect the integrity and confidentiality of user data. The malicious nature of this code was identified by security researchers from Amazon Inspector, highlighting the importance of vigilance when using open-source packages.

How To Fix

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

npm uninstall dspmgr

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, you may consider removing the dspmgr package from your project until a secure version is released. You can do this by running the command: 'npm uninstall dspmgr'. This will help mitigate the risk of exposure to the malicious code.

Conclusion

The discovery of malicious code in the dspmgr package highlights the critical need for developers to remain vigilant when using open-source libraries. Immediate action is required to update or remove the affected package to safeguard applications from potential threats. Utilizing tools like Vulert can further enhance security by providing real-time monitoring for vulnerabilities.

See every vulnerability recorded for dspmgr →

Share this vulnerability

FAQ

The dspmgr package is an npm library used for managing digital signal processing tasks in software applications.

The malicious code can potentially lead to unauthorized access and data breaches, compromising the security of applications that use this package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By analyzing your package-lock.json file, Vulert can help identify if your application is affected. You can also check the Vulert playground at Vulert Scanner without signing up.

If you cannot update the package right away, it is advisable to uninstall the dspmgr package to prevent any potential security risks until a secure version is available.

The malicious code was discovered by security researchers from Amazon Inspector, who are dedicated to identifying vulnerabilities in open-source packages.

How To Fix

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

npm uninstall dspmgr

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