Critical Vulnerability in node-buc Package

node-buc Updated 02 Oct 2025

Summary

03/09/2020
CRITICAL
No i
Critical
9.8

GHSA-x3m6-rprw-862w: Malicious Package in node-buc. Affects node-buc versions >= 0.0.0. 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 node-buc package is an npm package used for system information retrieval and management. It provides functionality to gather and process system data. Unfortunately, all versions of node-buc contain malicious code that uploads system information to a remote server, downloads a file, and executes it. This vulnerability poses a significant risk to any computer that has this package installed or running.

Vulnerability Detail

The malicious code present in all versions of node-buc allows an attacker to gain full control of the compromised computer. It uploads system information to a remote server, potentially exposing sensitive data. Additionally, it downloads and executes a file, which can lead to further malicious activities. As a result, any secrets and keys stored on the compromised computer should be rotated immediately from a different computer. Removing the package may not guarantee the removal of all malicious software installed as a result of its installation.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Conclusion

The node-buc package contains a critical vulnerability that allows attackers to gain full control of compromised systems. It is crucial to identify and remediate this vulnerability promptly. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for node-buc →

Share this vulnerability

FAQ

The impact of this vulnerability is severe. Any computer with the node-buc package installed or running should be considered fully compromised. Attackers can gain complete control of the system and potentially access sensitive information.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities using package-lock.json.

While removing the node-buc package is recommended, it may not completely remove all the malicious software installed as a result of its installation. A thorough security audit should be conducted to ensure the removal of any remaining compromises.

If your system is compromised, it is crucial to disconnect it from the network immediately to prevent further damage. Rotate all secrets and keys stored on the compromised system from a different, secure computer. Remove the node-buc package and conduct a comprehensive security audit to identify any other potential compromises or vulnerabilities.

To prevent this vulnerability, it is essential to regularly update and patch all software components, including npm packages. Additionally, practicing secure coding techniques and conducting regular security audits can help identify and mitigate potential vulnerabilities.

Related vulnerabilities

Recent vulnerabilities recorded for node-buc.

How To Fix

No fixed version is published for this vulnerability.

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