Malicious Code Injection in nokire-kore20: A Threat to npm Ecosystem
Summary
MAL-2025-162707: Malicious code in nokire-kore20 (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-kore20 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and deployment of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits the npm registry, potentially compromising the integrity of applications that depend on it.
Vulnerability Detail
The vulnerability in nokire-kore20 stems from its association with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only inflates developer reputation scores but also leads to the continuous republishing of these variants, polluting the npm registry and making it difficult for developers to identify legitimate packages. The malicious payload can compromise the security of applications that utilize this package, leading to potential data breaches or unauthorized access.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-kore20If 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-kore20 package from your project by executing 'npm uninstall nokire-kore20'. This will prevent any malicious code from executing while you assess the situation and look for a secure alternative package.
Conclusion
The nokire-kore20 package poses a significant threat due to its malicious code that exploits the npm registry. It is crucial for developers to remain vigilant, update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, the risks associated with such vulnerabilities can be mitigated.
See every vulnerability recorded for nokire-kore20 →
FAQ
The main risk is the potential for unauthorized modifications to your application's dependencies, which can lead to security breaches and data loss.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By using the Vulert playground, you can check if your application is affected without any signup.
If you cannot update the package, consider removing it from your project and looking for alternative packages that provide similar functionality without the associated risks.
The malicious code modifies the package.json file to remove private flags and changes version numbers, allowing it to republish variants that can pollute the npm registry.
To prevent future vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and ensure that you only install packages from trusted sources.
