Critical Malicious Code Vulnerability in baouncing Package

baouncing Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15462: Malicious code in baouncing (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 baouncing package is an npm library designed for managing asynchronous operations in JavaScript applications. It offers features that simplify the handling of callbacks and promises, making it a popular choice among developers. However, the package has been found to contain malicious code that poses significant security risks to applications utilizing it.

Vulnerability Detail

The vulnerability in the baouncing package stems from the inclusion of malicious code that can compromise the security of applications. This code may allow unauthorized access to sensitive data, execute arbitrary commands, or facilitate other malicious activities. The issue originated from the package's version 0 and affects all subsequent versions, making it imperative for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall baouncing

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, users can remove the baouncing package from their project until a secure version is released. This can be done using the command: npm uninstall baouncing. Alternatively, consider using a different package that offers similar functionality without the associated risks.

Conclusion

The baouncing package has been identified as containing malicious code that poses a significant security risk. Users are strongly advised to update or remove the package to protect their applications. Tools like Vulert can assist in monitoring for such vulnerabilities in real-time.

See every vulnerability recorded for baouncing →

Share this vulnerability

FAQ

The baouncing package is an npm library used for managing asynchronous operations in JavaScript applications.

The malicious code can compromise application security, potentially allowing unauthorized access to sensitive data or executing harmful commands.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground without signup.

If you cannot update the package right away, consider removing it from your project or using an alternative package until a secure version is available.

Utilizing tools like Vulert can help you monitor your dependencies for vulnerabilities and receive alerts in real-time.

How To Fix

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

npm uninstall baouncing

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