Malicious Code Detected in dampradio Package - Security Alert

dampradio Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17940: Malicious code in dampradio (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 dampradio package is an npm library designed for audio streaming and manipulation. It provides functionalities for developers to integrate audio features into their applications. However, it has been identified to contain malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the dampradio package stems from the inclusion of malicious code that can compromise the integrity of applications utilizing this package. This code can lead to unauthorized access, data breaches, or exploitation of user systems. The issue was introduced in all versions starting from 0, making every installation of this package potentially harmful.

How To Fix

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

npm uninstall dampradio

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, avoid using the dampradio package in your projects until a secure version is released. Consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The discovery of malicious code in the dampradio package highlights the importance of regularly monitoring open-source dependencies. Users are advised to remove the package and seek alternatives to safeguard their applications. Utilizing tools like Vulert can help in proactively identifying such vulnerabilities.

See every vulnerability recorded for dampradio →

Share this vulnerability

FAQ

The dampradio package is an npm library used for audio streaming and manipulation in applications.

The malicious code was identified by security researchers from Amazon Inspector, who monitor open-source packages for vulnerabilities.

Using the dampradio package can lead to unauthorized access to your application, data breaches, and potential exploitation of user systems.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

If you have used the dampradio package, it is recommended to uninstall it immediately and look for alternative packages to ensure your application's security.

How To Fix

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

npm uninstall dampradio

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