Malicious Code Injection in nokire-nana2: A Threat to npm Users
Summary
MAL-2025-163171: Malicious code in nokire-nana2 (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 'nokire-nana2' is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various applications to manage dependencies efficiently. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of derivative packages with randomized names. This vulnerability exposes users to potential risks, including the modification of their package configurations and the pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'nokire-nana2' originates from its involvement in the tea.xyz token reward campaign, which has led to the creation of numerous malicious packages. These packages contain scripts designed to automatically publish derivative versions with altered package.json files, removing private flags, changing version numbers, and generating random package names. This not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of control over their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-nana2If 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 avoid using the 'nokire-nana2' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for open-source vulnerabilities in real-time.
Conclusion
The 'nokire-nana2' package poses a significant risk to npm users due to its malicious nature and the potential for unauthorized modifications to project configurations. It is crucial to remove this package and monitor your projects for vulnerabilities to maintain security and integrity.
See every vulnerability recorded for nokire-nana2 →
FAQ
'nokire-nana2' is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your project's integrity and security.
You should uninstall the 'nokire-nana2' package immediately and check your project for any affected dependencies.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities by analyzing your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.
