Malicious Code Injection in nokire-kore27: A Threat to npm Ecosystem
Summary
MAL-2025-162714: Malicious code in nokire-kore27 (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-kore27' is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of code within the JavaScript community. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages, thereby inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in 'nokire-kore27' originates from its association with the tea.xyz token reward campaign. It includes malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-kore27If 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-kore27' package and replace it with a known, secure alternative. Always review the dependencies in your project and ensure they come from reputable sources.
Conclusion
The 'nokire-kore27' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure the security of their applications.
See every vulnerability recorded for nokire-kore27 →
FAQ
The primary risk is that it can compromise the integrity of your project by introducing malicious code that modifies your package.json and floods the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
You should uninstall the package immediately using the command 'npm uninstall nokire-kore27' and review your project's dependencies for any other vulnerabilities.
No patches are available for nokire-kore27 as it is a malicious package. The best course of action is to remove it from your project.
Regularly audit your dependencies, use trusted packages, and consider using tools like Vulert to monitor for vulnerabilities in real-time.
