Malicious Code Injection in baso13 Package: A Threat to npm Ecosystem
Summary
MAL-2025-181368: Malicious code in baso13 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The baso13 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 code among developers. However, baso13 has been identified as part of a malicious campaign that aims to exploit the npm registry by publishing derivative packages with harmful scripts.
Vulnerability Detail
The vulnerability in the baso13 package originates from its association with the tea.xyz token reward campaign. This campaign has led to the creation of numerous malicious packages that include scripts designed to automatically modify package.json files. These scripts remove private flags, alter version numbers, and generate random package names, ultimately leading to the pollution of the npm registry. The ramifications of this vulnerability include compromised developer reputation scores and potential security risks for applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall baso13If 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 baso13 package and replace it with a similar, trusted package that does not exhibit malicious behavior. Always verify the integrity of packages before including them in your project.
Conclusion
The baso13 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package.json files and publish harmful variants. It is essential to remove this package from your projects and monitor your dependencies for any similar vulnerabilities.
See every vulnerability recorded for baso13 →
FAQ
The baso13 package is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem.
The malicious code can modify your package.json file, remove private flags, and publish harmful variants, potentially compromising your application's security.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
If you have installed baso13, immediately uninstall it using npm uninstall baso13 and replace it with a trusted package.
Yes, there are multiple packages associated with the tea.xyz token reward campaign that may exhibit similar malicious behavior. Always review your dependencies.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
