Malicious Code in build-buf-action (npm)

build-buf-action Updated 02 Oct 2025

Summary

21/11/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8552: Malicious code in build-buf-action (npm). Affects build-buf-action versions 22.2.6. 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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The build-buf-action package is an npm package that is used for building and buffering actions. It provides functionality for executing commands associated with building and buffering actions. This package is vulnerable to a malicious code injection.

Vulnerability Detail

The build-buf-action package has been identified as malicious by the OpenSSF Package Analysis project. The package communicates with a domain associated with malicious activity and executes commands that are linked to malicious behavior. This vulnerability can lead to various security risks, including unauthorized access, data breaches, and the execution of arbitrary code.

How To Fix

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

npm uninstall build-buf-action

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

There is no specific workaround mentioned for this vulnerability. The best course of action is to follow the steps mentioned in the 'how_to_fix' section.

Conclusion

The build-buf-action package has been identified as malicious and poses a significant security risk. It is recommended to remove this package from your project and replace it with a trusted alternative. Regularly updating your packages is essential to mitigate the risk of known vulnerabilities. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for build-buf-action →

Share this vulnerability

FAQ

build-buf-action is an npm package used for building and buffering actions.

The build-buf-action package becomes vulnerable when it is used in a project and communicates with a domain associated with malicious activity.

This vulnerability can lead to unauthorized access, data breaches, and the execution of arbitrary code.

To fix this vulnerability, remove the build-buf-action package from your project and replace it with a trusted alternative. Regularly update your packages to ensure you are using the latest versions without known vulnerabilities.

There is no specific workaround mentioned for this vulnerability. Follow the steps mentioned in the 'how_to_fix' section.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall build-buf-action

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