Malicious Code Injection in nokire-nakala99: A Threat to npm Ecosystem
Summary
MAL-2025-163057: Malicious code in nokire-nakala99 (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-nakala99' is part of a series of malicious npm packages linked to the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior not only inflates developer reputation scores but also poses a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'nokire-nakala99' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This leads to the continuous republishing of variants, polluting the npm registry and potentially compromising other packages. The malicious scripts (auto.js, autopublish.js, etc.) are designed to automate this process, making it difficult for developers to track and manage their dependencies effectively.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-nakala99If 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 use the following command to prevent the installation of the malicious package: 'npm install --no-optional'. This will skip optional dependencies, which may include the malicious package.
Conclusion
The 'nokire-nakala99' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant, regularly check their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive steps, you can safeguard your applications from potential risks.
See every vulnerability recorded for nokire-nakala99 →
FAQ
The vulnerability can lead to the pollution of the npm registry, affecting the integrity of other packages and potentially compromising your application.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.
Immediately uninstall the package using 'npm uninstall nokire-nakala99' and review your dependencies for any other potential vulnerabilities.
Vulert uses your package-lock.json to monitor and alert in real-time for open-source vulnerabilities, providing a proactive approach to security.
Currently, there are no patches for 'nokire-nakala99' as it is recommended to remove the package entirely from your project.
