Malicious Code Detected in bud-live-server: A Critical Security Concern

bud-live-server Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16256: Malicious code in bud-live-server (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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'bud-live-server' is a tool designed for live reloading of web applications during development, allowing developers to see changes in real-time without refreshing the browser. It is widely used in the JavaScript ecosystem, particularly within npm packages. However, recent findings have revealed that this package contains malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in 'bud-live-server' stems from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code may lead to unauthorized access, data breaches, or other harmful actions within the user's environment. The malicious nature of the code was identified by security researchers, raising alarms about the potential impact on developers and their projects.

How To Fix

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

npm uninstall bud-live-server

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 measure, consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.

Conclusion

The discovery of malicious code in 'bud-live-server' highlights the importance of maintaining secure dependencies in software development. Developers are urged to update their packages and utilize tools like Vulert to monitor for vulnerabilities effectively.

See every vulnerability recorded for bud-live-server →

Share this vulnerability

FAQ

'bud-live-server' is a development tool that enables live reloading of web applications, enhancing the development workflow.

The malicious code was identified by security researchers from Amazon Inspector, who reported the vulnerability to the community.

Using the compromised version of 'bud-live-server' can lead to unauthorized access, data breaches, and potential exploitation of your application.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If immediate updates are not possible, consider using alternative packages and monitor your dependencies closely for any security alerts.

How To Fix

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

npm uninstall bud-live-server

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