Malicious Code Injection in nokire-nana9: A Threat to npm Users
Summary
MAL-2025-163248: Malicious code in nokire-nana9 (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 nokire-nana9 package 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 npm's publishing mechanisms. It is designed to automatically generate and publish derivative packages with altered metadata, thereby inflating developer reputation scores for token rewards in the tea.xyz protocol.
Vulnerability Detail
The vulnerability in nokire-nana9 stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can potentially compromise the integrity of other packages. The origin of this vulnerability is linked to a broader campaign that leverages npm's infrastructure for malicious purposes, posing risks to developers and users relying on npm packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-nana9If 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 nokire-nana9 package from your project by executing: npm uninstall nokire-nana9. This will prevent any malicious code from executing while you assess the situation.
Conclusion
The nokire-nana9 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with compromised packages. It is crucial for developers to stay vigilant, update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for nokire-nana9 →
FAQ
The main threat is the modification of package metadata, which can lead to the proliferation of malicious packages in the npm registry, potentially affecting other developers and users.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without needing to sign up.
If you cannot update the package, consider removing it from your project and replacing it with a safer alternative until a fix is available.
To prevent future vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about security advisories related to the packages you use.
Using a compromised package can lead to security breaches, data leaks, and the potential for your application to be used for malicious activities without your knowledge.
