Malicious Code Injection in baso14 Package: A Threat to npm Ecosystem
Summary
MAL-2025-181369: Malicious code in baso14 (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 baso14 package is part of the npm ecosystem, which is widely used for JavaScript development. It is typically utilized for various functionalities within applications, but it has been identified as part of a malicious campaign aimed at manipulating npm's package registry. This package is associated with the tea.xyz token reward scheme, which has led to the proliferation of numerous derivative packages that can compromise the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the baso14 package stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to inflate developer reputation scores for token rewards. This behavior not only pollutes the npm registry but also poses significant risks to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall baso14If 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 remove the baso14 package from your project by executing the command: 'npm uninstall baso14'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The baso14 package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential for developers to be aware of this vulnerability, take immediate action to remove the affected package, and utilize tools like Vulert to monitor their projects for potential vulnerabilities.
See every vulnerability recorded for baso14 →
FAQ
The baso14 package is a JavaScript library available on npm, which has been identified as part of a malicious campaign affecting the npm ecosystem.
The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.
If you have installed baso14, it is crucial to uninstall the package immediately and monitor for any updates or patches.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
