Malicious Code Injection in nokire-nana47: A Threat to npm Ecosystem
Summary
MAL-2025-163201: Malicious code in nokire-nana47 (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-nana47' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with random names, thereby inflating developer reputation scores for token rewards. The malicious nature of this package poses significant risks to developers and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'nokire-nana47' originates from its involvement in a malicious campaign that utilizes autopublish scripts to generate and publish derivative packages. This results in the modification of the package.json file by removing private flags, altering version numbers, and creating random package names. The continuous republishing of these variants leads to pollution of the npm registry, which can compromise the security and reliability of the packages available to developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-nana47If 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-nana47' package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package dependencies to identify and remove any potentially harmful packages.
Conclusion
The 'nokire-nana47' package poses a significant threat to the npm ecosystem due to its malicious code that modifies package.json and floods the registry with harmful variants. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for nokire-nana47 →
FAQ
The main risk is that it modifies your package.json file and floods the npm registry with malicious packages, which can compromise the integrity of your project.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
You should immediately uninstall the package using 'npm uninstall nokire-nana47' and audit your project for any other potentially malicious packages.
There are no patches available for nokire-nana47 as it is a malicious package. The best course of action is to remove it entirely.
Regularly audit your dependencies, use trusted packages, and stay informed about known vulnerabilities in the npm ecosystem.
