Critical Malicious Code Vulnerability in bud-babelify Package

bud-babelify Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16252: Malicious code in bud-babelify (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 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 bud-babelify package is a tool used in the JavaScript ecosystem, specifically designed to facilitate the integration of Babel with Bud, a modern build tool. It allows developers to transpile modern JavaScript code into a format compatible with older environments. However, this package has been compromised, leading to the introduction of malicious code that can potentially harm users' applications.

Vulnerability Detail

The vulnerability in bud-babelify stems from the inclusion of malicious code within the package. This code can execute harmful actions on the user's system, such as data exfiltration or unauthorized access to sensitive information. The malicious code was introduced in version 0 and affects all subsequent versions, posing a significant risk to developers who rely on this package for their projects.

How To Fix

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

npm uninstall bud-babelify

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 using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can analyze your package-lock.json file to identify potential threats.

Conclusion

The bud-babelify package has been identified as containing malicious code, posing significant risks to developers and their applications. It is essential to uninstall the package and monitor for updates or alternatives to ensure the security of your projects.

See every vulnerability recorded for bud-babelify →

Share this vulnerability

FAQ

bud-babelify is a package that integrates Babel with Bud, allowing developers to transpile modern JavaScript code.

The malicious code was introduced in version 0 of the bud-babelify package, affecting all subsequent versions.

Using bud-babelify can lead to data breaches, unauthorized access, and other harmful actions due to the malicious code present in the package.

You can use Vulert's playground to analyze your package-lock.json file and check for vulnerabilities without needing to sign up.

Immediately uninstall the package and consider using alternative solutions. Regularly monitor your dependencies for vulnerabilities.

How To Fix

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

npm uninstall bud-babelify

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