Critical Malicious Code Vulnerability in node-buc Package

node-buc Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-27608: Malicious code in node-buc (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 node-buc package is an npm library designed for utility functions in Node.js applications. It offers various features that enhance the development experience. However, it has been identified to contain malicious code, posing a significant risk to applications that utilize it. This vulnerability can lead to unauthorized access or manipulation of application data.

Vulnerability Detail

The vulnerability in the node-buc package originates from the inclusion of malicious code that can execute harmful actions within the user's environment. This code can compromise the integrity of applications, leading to data breaches or unauthorized access. The malicious nature of this vulnerability makes it critical for developers to address it immediately to safeguard their applications.

How To Fix

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

npm uninstall node-buc

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 can remove the node-buc package from your project until a secure version is available. You can do this by executing the following command: npm uninstall node-buc. This will prevent any malicious code from executing in your application.

Conclusion

The discovery of malicious code in the node-buc package presents a serious threat to applications that rely on it. Developers must act swiftly to update or remove the package to protect their applications from potential harm. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities in real-time.

See every vulnerability recorded for node-buc →

Share this vulnerability

FAQ

The node-buc package is an npm library that provides utility functions for Node.js applications.

The malicious code in node-buc can execute harmful actions that compromise application security and data integrity.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

Yes, it is recommended to update to the latest patched version of node-buc to mitigate the vulnerability.

If you cannot update the package right away, consider uninstalling it as a temporary measure to prevent any potential exploitation of the vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for node-buc.

How To Fix

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

npm uninstall node-buc

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