Malicious Code Injection in manda-32 Package: npm Vulnerability Overview
Summary
MAL-2025-159629: Malicious code in manda-32 (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-32 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages. This package has been identified as malicious due to its functionality that modifies package metadata and floods the npm registry with spammy packages, impacting the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in the manda-32 package originates from its malicious intent to manipulate package.json files by removing private flags and altering version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry, making it difficult for developers to find legitimate packages. The malicious code can lead to security risks, including the potential for further exploitation of affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall manda-32If 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-32 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can implement a script to monitor your package.json for unauthorized changes.
Conclusion
The manda-32 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 and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the integrity of your projects.
See every vulnerability recorded for manda-32 →
FAQ
The manda-32 package is an npm package involved in the tea.xyz token reward campaign, designed to generate and publish derivative packages automatically.
The vulnerability can lead to the pollution of the npm registry, making it harder to find legitimate packages and potentially exposing your project to security risks.
You should remove the manda-32 package from your project immediately and monitor your package.json for any unauthorized changes.
Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
