Malicious Code Injection in mansida-nomfmadi-mungu: A Threat to npm Users
Summary
MAL-2025-159756: Malicious code in mansida-nomfmadi-mungu (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 'mansida-nomfmadi-mungu' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior poses a significant risk to the integrity of the npm registry and the security of applications relying on these packages.
Vulnerability Detail
The vulnerability in 'mansida-nomfmadi-mungu' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants that pollute the npm registry, potentially leading to security risks for developers who unknowingly use these compromised packages. The malicious code is designed to exploit the npm ecosystem, making it crucial for users to be aware of this threat.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mansida-nomfmadi-munguIf 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 this package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will help avoid any unintended installations of this malicious package.
Conclusion
The 'mansida-nomfmadi-mungu' package poses a significant threat due to its malicious code designed to exploit the npm ecosystem. It is essential for developers to be vigilant, remove any instances of this package, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for mansida-nomfmadi-mungu →
FAQ
The main risk is that it contains malicious code that modifies package.json files and floods the npm registry with compromised packages, potentially affecting other developers.
You can check your package-lock.json file for the presence of 'mansida-nomfmadi-mungu' or use tools like Vulert to monitor for vulnerabilities.
Remove the package immediately and consider using Vulert to monitor your project for any other vulnerabilities.
Regularly audit your dependencies and use tools like Vulert to receive real-time alerts for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
