Malicious Code Injection in namae-nadugsua-mios Package
Summary
MAL-2025-161798: Malicious code in namae-nadugsua-mios (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 namae-nadugsua-mios package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random Indonesian-themed package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other developers by inflating reputation scores through deceptive practices.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall namae-nadugsua-miosIf 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 affected package from your project by executing the command: npm uninstall namae-nadugsua-mios. This will prevent any malicious code from executing in your environment until a fix is applied.
Conclusion
The namae-nadugsua-mios package has been identified as containing malicious code that compromises the npm registry. It is crucial for developers to update or remove this package to safeguard their applications. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.
See every vulnerability recorded for namae-nadugsua-mios →
FAQ
The malicious code can lead to the pollution of the npm registry and may affect other developers by inflating reputation scores through deceptive practices.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.
If immediate updates are not possible, consider uninstalling the package as a temporary measure to prevent any potential exploitation of the vulnerability.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.
Detailed information about this vulnerability can be found in the Open Source Vulnerability database or by checking the package's repository on npm.
