Malicious Code Injection in manda-33 Package: A Threat to npm Ecosystem
Summary
MAL-2025-159630: Malicious code in manda-33 (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-33 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 JavaScript code. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of derivative packages with randomized names. This behavior poses a significant risk to developers and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the manda-33 package originates from its association with the tea.xyz token reward campaign. The package contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This leads to the continuous republishing of variants, effectively polluting the npm registry and compromising the security of the ecosystem. Developers using this package may unknowingly contribute to the spread of malicious code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall manda-33If 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-33 package and replace it with a trusted alternative. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The manda-33 package poses a significant risk due to its malicious behavior, which can compromise the security of projects using it. It is essential to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the integrity of your software.
See every vulnerability recorded for manda-33 →
FAQ
The manda-33 package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You should immediately remove the manda-33 package from your project and monitor your dependencies for any further vulnerabilities.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
