Malicious Code Injection in nokire-kore5: A Threat to npm Packages
Summary
MAL-2025-162735: Malicious code in nokire-kore5 (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-kore5' is part of a series of npm packages that have been associated with 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 is intended to inflate developer reputation scores in exchange for token rewards, making it a significant concern for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in 'nokire-kore5' stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in a pollution of the npm registry, making it difficult for developers to trust the integrity of packages. The malicious payload is part of a broader scheme to exploit the npm ecosystem, potentially leading to security risks and loss of trust in the platform.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-kore5If 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-kore5' package and replace it with a trusted alternative. Additionally, you can use npm audit to identify and address vulnerabilities in your project.
Conclusion
The 'nokire-kore5' package poses a significant risk due to its malicious code that manipulates the npm registry. It is crucial for developers to be vigilant and regularly audit their dependencies to maintain the integrity of their applications. Utilizing tools like Vulert can aid in identifying vulnerabilities and ensuring a secure development environment.
See every vulnerability recorded for nokire-kore5 →
FAQ
The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use Vulert, which monitors open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
You should uninstall the package immediately using 'npm uninstall nokire-kore5' and check for any other affected packages.
Yes, tools like Vulert can help you monitor and alert you in real-time for open-source vulnerabilities using just your package-lock.json.
Using compromised packages can lead to security breaches, data loss, and a loss of trust in the npm ecosystem.
