Malicious Code Injection in manda-44: A Threat to npm Ecosystem
Summary
MAL-2025-159642: Malicious code in manda-44 (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 package 'manda-44' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that manipulate package metadata and publish derivative packages to inflate developer reputation scores, posing a significant risk to developers and their projects.
Vulnerability Detail
The vulnerability in 'manda-44' originates from its design to include malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also exposes developers to potential security risks and reputational damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall manda-44If 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 prevent the installation of 'manda-44' by using the following command: 'npm uninstall manda-44'. Additionally, ensure that your package-lock.json file is monitored for any unauthorized changes.
Conclusion
The 'manda-44' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry with harmful variants. It is essential for developers to take immediate action by updating or removing the package to safeguard their projects.
See every vulnerability recorded for manda-44 →
FAQ
The vulnerability involves malicious code that modifies package metadata and repackages it, leading to potential security risks.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.
If no patched version is available, consider removing the package from your project to mitigate risks.
Vulert uses your package-lock.json to monitor and alert you in real-time for open-source vulnerabilities in your software.
Using compromised packages can lead to security breaches, data loss, and damage to your project's reputation.
