Malicious Code Injection in baso71 Package: A Threat to npm Ecosystem
Summary
MAL-2025-181431: Malicious code in baso71 (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 baso71 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 reusable code components. However, baso71 has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security concerns for developers and users relying on this package.
Vulnerability Detail
The vulnerability in the baso71 package originates from its association with the tea.xyz token reward campaign. This package contains scripts that automatically generate and publish derivative packages with randomized names, effectively inflating developer reputation scores for token rewards. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, leading to pollution of the npm registry 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 baso71If 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 baso71 package and replace it with a secure alternative. Always verify the integrity and source of packages before including them in your project.
Conclusion
The baso71 package poses a significant threat to the npm ecosystem due to its malicious code injection capabilities. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help ensure ongoing security and integrity in your applications.
See every vulnerability recorded for baso71 →
FAQ
The baso71 package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
If you have installed baso71, you should uninstall it immediately using 'npm uninstall baso71' and review your project for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Yes, always look for well-maintained and widely used packages in the npm registry that serve the same purpose as baso71 but have a good reputation and community support.
