Critical Malicious Code Vulnerability in babel-node Package

babel-node Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15286: Malicious code in babel-node (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 babel-node package is a command line tool that is part of the Babel ecosystem, which is widely used for transpiling JavaScript code. It allows developers to run JavaScript files that use ES6+ syntax without pre-compiling them. However, the package has been found to contain malicious code, posing significant risks to users who rely on it for their development workflows.

Vulnerability Detail

The vulnerability in the babel-node package arises from the inclusion of malicious code that can compromise the security of applications utilizing this package. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the user's environment. The issue originates from the package's codebase, which was intentionally altered to introduce these vulnerabilities, making it critical for users to take immediate action.

How To Fix

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

npm uninstall babel-node

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, users can avoid using the babel-node package until the vulnerability is fully addressed. Alternatively, consider using other transpilation tools that do not have known vulnerabilities.

Conclusion

The discovery of malicious code in the babel-node package highlights the importance of maintaining vigilance when using open-source software. Users are strongly encouraged to update their packages and monitor for vulnerabilities to safeguard their applications.

See every vulnerability recorded for babel-node →

Share this vulnerability

FAQ

babel-node is a command line tool that allows developers to run JavaScript files using Babel's transpilation capabilities without pre-compiling them.

The malicious code can lead to unauthorized access and potential data breaches, posing significant security risks to applications using this package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

As a temporary measure, avoid using the babel-node package until a fix is implemented, or consider using alternative tools for transpilation.

Detailed information about the vulnerability can be found on the GitHub repository of the malicious package: https://github.com/ossf/malicious-packages/blob/main/osv/malicious/npm/babel-node/MAL-2025-15286.json.

How To Fix

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

npm uninstall babel-node

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