Malicious Code Injection in baso54: A Threat to npm Users
Summary
MAL-2025-181412: Malicious code in baso54 (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The baso54 package is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of JavaScript code. However, baso54 has been identified as part of a malicious campaign that aims to exploit npm's publishing capabilities, leading to potential security risks for developers and their applications.
Vulnerability Detail
The vulnerability in baso54 stems from its association with the tea.xyz token reward campaign, which has led to the creation of numerous malicious packages. These packages contain scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, making it difficult for users to find legitimate packages. The malicious payload can lead to unintended consequences, such as the installation of compromised packages and exposure of sensitive data.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall baso54If 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, you can avoid using the baso54 package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The baso54 package poses a significant threat to npm users due to its malicious code designed to exploit the npm registry. It is crucial for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can protect their applications from potential security risks.
See every vulnerability recorded for baso54 →
FAQ
The baso54 package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
The malicious code can modify your package.json file, remove private flags, and publish derivative packages, potentially leading to security vulnerabilities and data exposure.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By utilizing the Vulert playground, you can check if your application is affected without any signup.
If you have installed baso54, you should uninstall it immediately using the command npm uninstall baso54 and review your project for any other potentially malicious packages.
There are no patches available for baso54 as it is a malicious package. The best course of action is to remove it from your project.
