Malicious Code Injection in manda-37: A Threat to npm Packages
Summary
MAL-2025-159634: Malicious code in manda-37 (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-37 is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate the distribution of software packages within the npm ecosystem. However, this package has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with derivative packages. This behavior not only harms the reputation of developers but also poses a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in manda-37 originates from its inclusion in a malicious campaign aimed at inflating developer reputation scores for token rewards. The package contains scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This results in the continuous republishing of these variants, which can lead to registry pollution and potential exploitation by malicious actors. The technical implications include the risk of unintentional dependency on compromised packages and the degradation of the npm registry's reliability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall manda-37If 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 measure, you can avoid using the manda-37 package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package.json file does not include any references to manda-37.
Conclusion
The manda-37 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the integrity of your software.
See every vulnerability recorded for manda-37 →
FAQ
The primary risk is the potential for malicious code execution and the pollution of the npm registry, which can lead to the installation of compromised packages.
You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can identify if your application is affected. You can check your application using the Vulert playground at Vulert Scanner.
If you have installed manda-37, you should uninstall it immediately using the command npm uninstall manda-37 and look for alternative packages.
While specific alternatives depend on the functionality you require, consider searching the npm registry for similar packages that do not have known vulnerabilities.
Regularly check for updates to your packages and use tools like Vulert to monitor your dependencies for any emerging vulnerabilities.
