Critical Malicious Code Vulnerability in buenas Package

buenas Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16262: Malicious code in buenas (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 buenas package is an npm library designed to facilitate various functionalities in JavaScript applications. It is commonly used for its ease of integration and lightweight nature. However, it has been identified to contain malicious code, posing significant risks to applications that rely on it.

Vulnerability Detail

The buenas package has been found to contain malicious code that can compromise the security of applications using it. This vulnerability originated from the package itself, which was introduced in version 0 and has persisted in all subsequent versions. The ramifications include potential data breaches, unauthorized access, and exploitation of the application’s environment, making it critical for developers to address this issue immediately.

How To Fix

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

npm uninstall buenas

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 replacing the buenas package with an alternative library that provides similar functionality without the associated risks. Review your application's dependencies and ensure that no other packages are dependent on buenas.

Conclusion

The buenas package has been identified as containing malicious code, posing significant security risks to applications. It is crucial for developers to uninstall the package and consider alternatives to safeguard their applications. Regular monitoring of dependencies using tools like Vulert can help prevent future vulnerabilities.

See every vulnerability recorded for buenas →

Share this vulnerability

FAQ

The buenas package is an npm library used in JavaScript applications for various functionalities. It has been flagged for containing malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file, you can determine if your application is affected by this vulnerability.

If immediate removal is not possible, consider using an alternative library that offers similar functionality while ensuring your application remains secure.

Currently, there is no patched version available for the buenas package. It is recommended to uninstall it until a secure version is released.

Utilize tools like Vulert to monitor your dependencies for vulnerabilities. You can check your application using the Vulert playground without any signup.

How To Fix

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

npm uninstall buenas

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