Malicious Code Injection in manda-10: A Threat to npm Ecosystem
Summary
MAL-2025-159605: Malicious code in manda-10 (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
manda-10 is a package within the npm ecosystem that has been implicated in a malicious campaign targeting developers. It is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This package, like others in the campaign, is designed to manipulate the npm registry, posing a significant risk to users and developers relying on npm for package management.
Vulnerability Detail
The vulnerability in manda-10 stems from its inclusion in a malicious campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. These scripts modify the package.json file to remove private flags, alter version numbers, and continuously republish variants, leading to pollution of the npm registry. This not only compromises the integrity of the npm ecosystem but also exposes developers to potential security risks and reputational damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall manda-10If 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 manda-10 package and replace it with a trusted alternative. Additionally, you can implement strict package management practices by using tools like npm audit to identify and mitigate vulnerabilities in your project.
Conclusion
The manda-10 package poses a serious threat to the npm ecosystem due to its malicious code and association with a harmful campaign. Developers are urged to remove this package, monitor their dependencies for vulnerabilities, and utilize tools like Vulert for ongoing security assessments.
See every vulnerability recorded for manda-10 →
FAQ
The main risk is that it allows malicious code to be injected into your project, potentially compromising your application's security and integrity.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.
If you have installed manda-10, it is crucial to remove it immediately and replace it with a secure alternative. Regularly audit your dependencies for vulnerabilities.
Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your project's dependencies.
The tea.xyz token reward campaign aims to inflate developer reputation scores by flooding the npm registry with derivative packages, which can lead to significant pollution and security risks within the ecosystem.
