Malicious Code Injection in namadata-munaroha-manukangia Package
Summary
MAL-2025-161769: Malicious code in namadata-munaroha-manukangia (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-munaroha-manukangia package is part of the npm ecosystem, typically used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. This package, like others in the campaign, is designed to manipulate npm's publishing system, potentially affecting developers' reputations and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the namadata-munaroha-manukangia package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. This behavior can pollute the npm registry and inflate developer reputation scores fraudulently. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall namadata-munaroha-manukangiaIf 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-munaroha-manukangia package from your project by executing: npm uninstall namadata-munaroha-manukangia. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The namadata-munaroha-manukangia package contains a significant vulnerability due to its malicious code, which can compromise the integrity of the npm registry. It is essential to take immediate action by updating or uninstalling the package to safeguard your project. Regular monitoring of dependencies using tools like Vulert can help prevent future vulnerabilities.
See every vulnerability recorded for namadata-munaroha-manukangia →
FAQ
The vulnerability involves malicious code that alters package.json files, removes private flags, and generates random package names, leading to potential npm registry pollution.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without any signup.
As a temporary measure, you can uninstall the package to prevent any malicious actions until a secure version is released.
Uninstalling the package will not cause data loss, but ensure that you have backups of your project and dependencies before making changes.
Using compromised packages can lead to security breaches, data leaks, and damage to your project's reputation. It's crucial to regularly audit dependencies.
