Malicious Code Injection in namadata-munaro-nagama Package
Summary
MAL-2025-161760: Malicious code in namadata-munaro-nagama (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 namadata-munaro-nagama package is part of the npm ecosystem, which is widely used for JavaScript package management. This package 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 designed to manipulate package metadata and inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in the namadata-munaro-nagama package originates from its association with 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 can result in compromised developer accounts, loss of control over package versions, and potential security risks for applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall namadata-munaro-nagamaIf 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 remove the namadata-munaro-nagama package from your project by executing the following command: npm uninstall namadata-munaro-nagama. This will prevent any malicious code from executing while you assess the situation.
Conclusion
The namadata-munaro-nagama package contains a significant vulnerability due to malicious code that alters package metadata and floods the npm registry. It is crucial to update or remove this package to protect your applications from potential security risks.
See every vulnerability recorded for namadata-munaro-nagama →
FAQ
The malicious code is designed to modify package metadata and republish variants to inflate developer reputation scores.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
The risks include compromised developer accounts, loss of control over package versions, and potential security threats to applications using the affected package.
Check the npm registry for any updated versions of the namadata-munaro-nagama package that may contain security patches.
Consider removing the package from your project as a temporary measure to mitigate the risk until you can apply an update.
