Malicious Code Injection in manda-30 Package: npm Vulnerability Overview
Summary
MAL-2025-159627: Malicious code in manda-30 (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 manda-30 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for token rewards. Its functionality is compromised by malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in the manda-30 package stems from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall manda-30If 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-30 package and consider alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The manda-30 package poses a significant risk due to its malicious code designed to manipulate package metadata and flood the npm registry. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your projects.
See every vulnerability recorded for manda-30 →
FAQ
The manda-30 package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising security and causing issues with package management.
You should immediately remove the manda-30 package from your project and monitor your dependencies for any other vulnerabilities.
You can use tools like npm audit to check for vulnerabilities in your project. Additionally, Vulert can monitor your package-lock.json file for real-time alerts on open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
