Malicious Code Injection in manda-43: A Threat to npm Ecosystem
Summary
MAL-2025-159641: Malicious code in manda-43 (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-43' 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, like others in its category, utilizes scripts that manipulate package metadata to inflate developer reputation scores for token rewards. Its functionality is compromised by malicious code that alters package.json files and floods the npm registry with unwanted variants.
Vulnerability Detail
The vulnerability in 'manda-43' originates from its malicious payload, which modifies 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. The malicious code is part of a broader scheme to exploit the npm ecosystem for token rewards, leading to potential security breaches and loss of trust in package integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall manda-43If 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-43' package and replace it with a trusted alternative. Regularly audit your package dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The manda-43 package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to be vigilant, remove compromised packages, and utilize tools like Vulert to monitor for vulnerabilities in their applications.
See every vulnerability recorded for manda-43 →
FAQ
The manda-43 package contains malicious code that alters package metadata and floods the npm registry with unwanted variants.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without any signup.
You should uninstall the manda-43 package immediately using 'npm uninstall manda-43' and replace it with a trusted alternative.
Using the manda-43 package can lead to security breaches, loss of trust in your software, and potential exploitation of your application.
Regularly audit your dependencies, use trusted packages, and stay updated on security advisories related to the npm ecosystem.
