Critical Malicious Code Vulnerability in beep-types Package

beep-types Updated 05 Dec 2025

Summary

04/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192296: Malicious code in beep-types (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The beep-types package is an npm library that is typically used for handling beep sound types in JavaScript applications. It is designed to provide developers with a simple way to integrate sound notifications into their applications. However, this package has been compromised, leading to severe security risks for any system that has it installed.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the beep-types 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 origin of this vulnerability is linked to a malicious actor who has manipulated the package, making it a significant threat to users and their systems.

How To Fix

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

npm uninstall beep-types

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 workaround, it is recommended to rotate all secrets and keys stored on the affected computer from a different, secure machine. This step is essential to mitigate the risk of unauthorized access.

Conclusion

The beep-types package has been identified as containing malicious code that poses a significant risk to systems that have it installed. Users are advised to remove the package immediately and take steps to secure their sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for beep-types →

Share this vulnerability

FAQ

beep-types is an npm library used for managing beep sound types in JavaScript applications.

If you have the beep-types package installed, your system may be compromised. You can use Vulert to check your application for vulnerabilities.

Immediately remove the beep-types package and rotate any sensitive information stored on your system.

Currently, there is no patched version available. The best course of action is to remove the package entirely.

Vulert monitors and alerts for open-source vulnerabilities in your software using the package-lock.json file, providing real-time insights without requiring code access.

How To Fix

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

npm uninstall beep-types

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