Malicious Code Injection in nokire-nana91: A Threat to npm Packages
Summary
MAL-2025-163250: Malicious code in nokire-nana91 (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-nana91' 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. The malicious nature of this package lies in its ability to manipulate package metadata and publish unauthorized versions, thereby compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'nokire-nana91' originates from its association with the tea.xyz token reward campaign, which employs scripts to automatically generate and publish numerous derivative packages. These scripts modify the package.json file to remove private flags, alter version numbers, and create random package names, leading to pollution of the npm registry. This not only affects the reputation of legitimate developers but also poses security risks to applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-nana91If 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, you can avoid using the 'nokire-nana91' package and replace it with a known, secure alternative. Regularly audit your package dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The 'nokire-nana91' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata. It is crucial for developers to be vigilant and regularly audit their dependencies to mitigate such risks. Utilizing tools like Vulert can aid in real-time monitoring of vulnerabilities.
See every vulnerability recorded for nokire-nana91 →
FAQ
The main issue is that it contains malicious code designed to manipulate package metadata and flood the npm registry with unauthorized versions.
You can use Vulert to monitor your application for vulnerabilities. By simply uploading your package-lock.json file, Vulert will alert you in real-time about any open-source vulnerabilities.
Using compromised packages can lead to security breaches, data leaks, and a tarnished reputation for developers, as well as potential legal implications.
Yes, regularly auditing your dependencies, using trusted sources, and keeping your packages updated can significantly reduce the risk of vulnerabilities.
You should uninstall the package immediately and review your project's dependencies for any other potentially malicious packages.
