Malicious Code Injection in namae-naga-nuo: A Threat to npm Packages
Summary
MAL-2025-161811: Malicious code in namae-naga-nuo (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 'namae-naga-nuo' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry and potential security risks for developers using these packages.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the 'namae-naga-nuo' package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these compromised packages. The continuous republishing of variants can lead to a cluttered environment, making it difficult for developers to identify legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall namae-naga-nuoIf 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 measure, avoid using the 'namae-naga-nuo' package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your package-lock.json file to identify and remove any potentially malicious packages.
Conclusion
The 'namae-naga-nuo' package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and flooding the registry. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Taking immediate action to remove such packages can help maintain the integrity of your projects.
See every vulnerability recorded for namae-naga-nuo →
FAQ
The 'namae-naga-nuo' package is an npm package that has been identified as part of a malicious campaign to flood the npm registry with derivative packages.
This vulnerability can lead to the installation of malicious packages, compromising the security and integrity of your project.
You should uninstall the 'namae-naga-nuo' package immediately and audit your dependencies for any other malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
