Malicious Code Injection in baso49: A Threat to npm Ecosystem
Summary
MAL-2025-181406: Malicious code in baso49 (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 package baso49 is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized by developers to share and manage code libraries efficiently. However, baso49 has been identified as part of a malicious campaign that aims to exploit the npm registry by generating and publishing derivative packages with harmful scripts. This vulnerability poses a significant risk to developers who may unknowingly integrate compromised packages into their projects.
Vulnerability Detail
The vulnerability in baso49 originates from its involvement in the tea.xyz token reward campaign, which floods the npm registry with 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 for token rewards but also pollutes the npm registry with potentially harmful packages. The ramifications include the risk of integrating malicious code into applications, leading to security breaches and compromised software integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall baso49If 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 baso49 and any other packages associated with the tea.xyz campaign. Regularly audit your project's dependencies using tools like npm audit to identify and remove any potentially harmful packages.
Conclusion
The baso49 package poses a significant threat to the npm ecosystem due to its malicious code injection capabilities. Developers must take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for baso49 →
FAQ
Baso49 is an npm package that has been identified as part of a malicious campaign targeting the npm registry.
The vulnerability can lead to the integration of malicious code into your application, potentially compromising its security and functionality.
You should remove baso49 from your project and check for any other affected packages. Use npm update to ensure you are using secure versions.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
