Malicious Code Injection in manda-47: A Threat to npm Ecosystem
Summary
MAL-2025-159645: Malicious code in manda-47 (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-47 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package 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. The malicious nature of this package lies in its ability to manipulate package metadata and flood the npm registry with harmful variants.
Vulnerability Detail
The vulnerability in manda-47 stems from its inclusion in a campaign that utilizes autopublish scripts to create and publish numerous derivative packages with randomized names. These scripts modify the package.json file by removing private flags, altering version numbers, and generating random package names, which can lead to pollution of the npm registry. This not only affects the integrity of the registry but also poses a risk to developers who may unknowingly install these malicious packages, potentially compromising their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall manda-47
If 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-47 package and instead look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before installation.
Conclusion
The manda-47 package poses a significant threat to the npm ecosystem due to its malicious code that modifies package metadata and floods the registry with harmful variants. It is crucial for developers to be vigilant and remove any affected packages from their projects while utilizing tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for manda-47 →
FAQ
manda-47 is an npm package involved in a malicious campaign that generates and publishes derivative packages to inflate developer reputation scores.
The vulnerability can lead to the installation of malicious packages that may compromise your application's security and integrity.
You should uninstall the manda-47 package immediately using the command npm uninstall manda-47 and check your project for any other affected packages.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Yes, you should look for reputable packages that serve similar purposes but do not have a history of malicious activity.